How do Projects work?

Purpose of a project

Projects serve the purpose of grouping prompts together. You might group projects together for various reasons. For example, you might want to clone a series of prompts for one campaign, you might need a series of prompts for article hero images, or you may want to group a set of reference image prompts with a final video prompt. Projects can be created for personal use or they can be associated with a team.

For more advanced projects, such as scenes for a video, projects can be attached to a Brief and contain a list of Scenes & Shots. This provides you with a high level of control over prompts inside a project. Briefs drive the core advanced workflow in Lorvara.

Projects anatomy

Start by creating a new project, from the dashboard. You will be presented with a dialog asking you to name the project, with optional description and hashtags. Here, you can also choose to create a project with a brief. A project without one is normal, not incomplete.

(Claude: add image of create-new-project here)

A project page shows you the following information:

Block	What it is for
Brief	Which brief this project uses, a summary once it is settled, and the Models this project’s shots are composed for.
Scenes & Shots	The shot list, the work order for this shoot.
Batch prompts	What Confirm & compose on the shot list filled. Composing writes the prompts; it does not generate a picture or a video. It is charged per prompt, and the button says the price.

Below that are Key Prompts, that are associated with the project with search, a status filter, and sort pills: Last Updated, Recently Created, A-Z, Z-A.

Each prompt in the grid gives you the whole set of actions: depending on whether you are in list view or card view, you can approve a prompt, open the Prompt Agent to read that prompt and help you modify it, or use the ⋯ menu for settings, clone and delete. Buttons are conveniently located in the prompt rows or cards that take you to its Studio, its Library, a connected Brief and Scenes & Shots.

Status and team are set here, not filtered here. The controls on the right of the toolbar change status of the project and the team the project is assigned to. The controls on the left filter change the data loaded into the table based on your choices.

Project status

Four states, and they are for you rather than for the system: nothing is withheld or deleted because of them.

Status	Means
Active	Being worked on now.
On hold	Paused, coming back.
Completed	Delivered. Kept, not archived.
Archived	Out of the way. Still there when you want it.

Prompt status

Inside a project, each Key Prompt is Working or Approved. Approved is a judgment you make about the output, not a state the system reaches on its own. It is how you separate what is finished from what is still moving, and it drives the status filter above the grid.

Moving a project to a team

Change team on the toolbar hands the project to a team, so everyone with a full seat can work in it. Its storage then counts against the team’s rather than your own. See How do Teams work?.

Setting project thumbnail and approval options on cards

A project’s thumbnail is set from within the card view using the Star icon in the top left corner. In addition, you have the option to review the prompt card thumbnails and approve a prompt using the Thumb in the bottom left of the card. You can also open the Prompt Agent on that prompt from its card.

What a cloned prompt carries: the prompt text, its parameters, its styles and its references. What it does not carry: the original’s generated media (a clone starts with an empty library) and, for video, the start and end frames, which are specific enough to the shot that inheriting them is almost never what you meant.

Finding a project

Once you have more than a handful, the toolbar above the list is how you get back to one:

Search by name.
Filter by team and by status (Active, Completed, On Hold, Archived). Archived projects are hidden until you switch them on.
Sort, including plain Name A–Z when you know what it is called.
Show 10, 25, 50 or 100 records at a time.

Note you can click the padlock to save the number of records preference.

Advanced project knowledge

A project with a brief can set default image and video models that will persist across prompts, and that is deliberate. Two projects can use the same brief as a means of generating prompts on different models, for example. Default models are set in the Brief block.

(claude, add image of projects-brief-block)

Prompts composed for the project are written to fit that model’s prompt limit, so the choice is not only a convenience: it shapes what gets written. Note that if no models are set for the prompts at the project level, composition uses Lorvara’s defaults for that mode, and those models will be chosen when the prompt is opened in the Studio for editing or generation.

A brief is attached to a project; it does not copy the brief into a project. Correct something in a brief and every project using it has the correction the next time a prompt is composed. When a change is meant for one project only, clone the brief first. See Reusing a brief.

Need to associate a number of projects together? The next level of organization would be at the team level. So teams can be created and named to organize a group of projects for larger productions.