Managing Projects
As your project list grows, the management tools let you stay organised and in control of who can do what.
Each project uses the same in-page navigation row across the workspace, Project Details, and Dependency Map views. The project name stays visible on that row, the selected section is highlighted in the centered tabs, and switching sections keeps you inside the same project context. When tracked dependency issues exist, the Dependency Map tab shows a small hoverable status dot instead of a large text badge.
Project Detail View
Section titled “Project Detail View”Click any project in the Projects list to open its detail view. From here you can:
- Edit the project name and description.
- Check the processing status — see whether documents are still being indexed or are ready.
- Manage Files — upload new documents, view existing ones, re-process or delete files.
- Review generation history — see all Audio, Video, and Infographic jobs that have been run, along with their status and progress.
- Manage Permissions — grant or revoke access for individual users or entire Teams.
For project-level spend, storage, and activity trends, use the project tabs and open Project Details.
Project Details
Section titled “Project Details”Use the Project Details screen when you need a higher-level view of how a project is being used.
- See running spend across project generation activity.
- Compare output mix by job type and model usage.
- Review recent source uploads, storage footprint, and contributor activity.
- Spot tracked follow-up actions such as image regenerations or final render passes.
Open a project, then use the centered tabs in the project header row to switch between Workspace, Project Details, and Dependency Map.
The project overflow menu no longer repeats those navigation destinations. It is reserved for project-specific actions such as configuration and deletion.
Project Access Levels
Section titled “Project Access Levels”ADD CREATE uses a permission system to control what each person can do within a project:
| Level | What it allows |
|---|---|
| Read | View the project, its files, and completed artifacts |
| Write | Upload files, run generation jobs, and view artifacts |
| Admin | Full access: manage permissions, edit project details, and delete the project |
Granting Access
Section titled “Granting Access”Permissions can be granted to:
- Individual users — by their email address.
- Teams — all members of the team inherit the team’s permission level on this project.
Generation History
Section titled “Generation History”Every generation request creates a job record you can track from the project detail view or Studio. Jobs go through the following stages:
| Stage | What it means |
|---|---|
| Queued | The job has been submitted and is waiting to start |
| Running | The pipeline is actively generating |
| Succeeded | The artifact is ready to view and download |
| Failed | Something went wrong — an error message will be shown |
Progress is tracked as a percentage throughout the job, so you can see how far along it is.
Deleting a Project
Section titled “Deleting a Project”Deleting a project permanently removes all of its source files, indexed knowledge, generation jobs, and produced artifacts (audio files, videos, infographics, transcripts, and grounding reports). This action cannot be undone.
Advanced Usage Notes
Section titled “Advanced Usage Notes”Use these patterns to get more predictable results:
- Keep inputs specific and scoped to one intent per generation request.
- Save intermediate outputs often, especially before running major edits or regenerations.
- Use review and assignment workflows early to reduce rework late in the lifecycle.
Troubleshooting
Section titled “Troubleshooting”If results are not what you expected:
- Verify source quality first (missing context, inconsistent structure, or conflicting inputs reduce output quality).
- Re-check selected options and audience/profile settings before re-running.
- If a job fails repeatedly, wait briefly and retry once; then escalate with the artifact or job context.
Frequently Asked Questions
Section titled “Frequently Asked Questions”Why did quality change between runs?
Section titled “Why did quality change between runs?”Different input context, settings, and model/runtime conditions can produce different outputs.
Should I regenerate or manually edit?
Section titled “Should I regenerate or manually edit?”Regenerate when the core structure is wrong; manually edit when only wording, ordering, or style needs adjustment.
What is the best way to reduce iteration cycles?
Section titled “What is the best way to reduce iteration cycles?”Start with clear scope, run smaller batches, and use review checkpoints after each major step.