Welcome!
-
-
- Learn Home
- Core Concepts
- Companies and Departments
- Courses
- Course Status and Visibility
- Sections
- Video Activities
- Reading Activities
- Document Activities
- Enrolling People in a Course
- Bulk Enroll With CSV
- Roles in a Course
- How Progress Is Tracked
- Course Reports
- Knowledge Base Overview
- Libraries and Folders
- Uploading Content Items
- Library Visibility
- AI Agent per Library
- My Courses
- Platform People
-
- Project Structure Template
- Table of Contents (TOC)
- Content Folder
- Introduction to Markdown
- Markdown Basics
- Markdown Lists
- Markdown Links
- Markdown Images
- Markdown Code
- Markdown Tables
- Markdown Equations
- Markdown Videos
- Markdown Embedded HTML
- VS Code Snippets
- Introduction to Styles
- Framed Narrations
- Markdown Configuration
- Editor Setup
-
Workspace Overview
TL;DR; The Workspace is the pair of entries at the top of the Create menu: Projects and Builds. A project is a named container inside a department that Lupo records video builds against; a build is one render run. Projects do not store your files — uploads are processed in the background and the finished video reaches you by email. Most accounts have one project and rarely need to think about it.
When you open the Create menu in Lupo, the first two entries are Projects and Builds, above the Creation Tools. Together they are your Workspace: the record of which videos were rendered, under which project, by whom, when, and how many minutes they consumed.
Most new users can ignore this for a while. Your account comes with one project, created when the account was set up, and the PowerPoint uploads you make are recorded against it automatically. The Workspace matters once you want to look up a past render, check how many minutes your team has left, or keep several teams' renders under separate projects.
Departments and projects
Lupo's workspace has two levels:
- Departments are the top level. They usually map to a team inside your organization: "HR", "Sales Enablement", "Product Training", "Compliance". Each department carries its own plan and its own pool of video minutes. Departments are set up with your plan; a team manager can see theirs under My Departments in the Create menu, and team members don't manage them.
- Projects live inside a department. A project has a name, a department and — only on the Markdown path that the Lupo team sets up on request — a connected GitHub repository with a default branch. That is the whole record. A project holds no uploaded decks, PDFs, links or finished videos; what accumulates under it is its list of builds.
The Department filter at the top of the Projects page is always there, whatever your plan. If you are the only person on your plan you will see one department in it, with your project's name next to it.
What a project does and does not hold
A project is the record that ties builds to a plan. Each build stores who started it, when, how long it ran, the minutes it consumed and whether it completed or failed, and it links to the finished video once the render is done.
What a project does not hold:
- The
.pptxyou upload. It is read once for the render and isn't filed anywhere you can browse. The finished video is: the Builds page keeps every build, with a Play button that opens it. - Anything from the other Create tools. PowerPoint → Narration, Google Slides → Video, PDF → Slides and Re-narrate Existing Video take no project at all. Their results come back by email, and nothing from them appears in your Workspace.
How builds get into the workspace
Two things create a build:
- PowerPoint → Video. Every upload is recorded as a build. If your account has a project without a repository — the usual case, and the one created at sign-up — the upload page shows Uploads will be saved to project: followed by its name, and the build lands there. The Create video button on a project row opens the same upload page with that project preselected. If your account has no project of its own, the upload still works: the build is recorded under Lupo's shared default project, which does not appear in your list, and the video reaches you by email as usual.
- Generate on a repository-backed project. A project connected to a GitHub repository — the Markdown path, set up by the Lupo team — shows a Generate button that renders a branch of that repository. See Video Builds.
There is no target-project selector on the Create tools for customers. The confirmation "Videos will be saved to selected project." comes from a selector that only Lupo administrators see on the PowerPoint upload page.
When to care about the workspace
Most of the time, you don't. But there are three moments when it pays off:
- When you want to find a past render. The Builds page lists every build with its date, who started it, its status and a Play button for the finished video.
- When you want to know how many minutes are left. The summary above the Builds list shows Available Minutes for the period, alongside Build Count, Total Minutes (the allowance, not what you used), Premium Minutes, Completed Builds and Failed Builds. Those figures cover the whole department, so filtering the list to one project doesn't narrow them.
- When several teams share one Lupo account. A team manager can create one project per team so each team's builds are listed separately.
If none of those apply, leave your one project alone and move on.
Where to go next
- Projects — what the Projects page shows, and what a project row links to.
- Video Builds — the Builds page, and what the Generate button really does.