Project Details

Project Details gives you an analytics-style view of a single project’s activity so you can understand usage without digging through individual assets one by one.

When To Use Project Details

Open this page when you need to answer questions such as:

How much has this project spent so far?
Which output types are being used the most?
Who has been most active in the project?
How much source material and generated content is this project storing?
Are follow-up actions such as regenerations or final renders increasing?

How To Open It

Open the project from the Projects list.
Use the project tabs at the top of the page.
Select Project Details.

The same tab row is used on the workspace and Dependency Map pages, so you can move between sections without leaving the project context.

That header row keeps the project name visible while the centered tabs switch sections, so Project Details uses the same top-level layout as the rest of the project workspace.

What You Will See

Summary Cards

The top section highlights the most important project signals:

Running project spend
Delivered asset count
Source file volume
Most active contributor

Activity Timeline

The activity timeline combines:

Source uploads
New generation jobs
Tracked follow-up actions

Use it to spot busy periods, spikes in iteration, or recent usage slowdowns.

Spend Composition

Spend is grouped into user-friendly categories so you can quickly see whether costs are coming from:

LLM usage
Image generation
Audio generation
Video or render activity
Other model override activity

Storyboard transition previews that use animated video generation are included in video spend, so Veo preview costs are visible even before a final video is rendered.

Project spend now comes from request-level usage events whenever available. That means model attribution is based on the actual LLM, image, audio, and video requests recorded for the project instead of being evenly split across an artifact after the fact.

Asset And Model Mix

Use the breakdown sections to compare:

Job volume by output type
Spend by model
Runtime and activity trends across project work

The model footprint includes models used by tracked storyboard follow-up actions, including Veo models used for animated transition previews.

Older artifacts created before request-level tracking was introduced are backfilled into the ledger automatically during startup when their stored cost summaries contain enough information to reconstruct historical usage.

If a legacy artifact still lacks reconstructable cost detail, Project Details falls back to its stored artifact summary for that row.

Contributors And Source Files

The lower sections help you answer operational questions:

Which users are creating or refining the most work?
Which source formats are most common in the project?
Which documents were added most recently?

Best Practices

Use Project Details before large rerun cycles so you understand the current project baseline.
Review the activity and spend sections together; high iteration often explains cost spikes.
Check contributor and source-file trends before adjusting prompts or brand settings for the whole team.

Troubleshooting

If the page looks sparse:

Confirm the project already has generated assets or recent uploads.
Refresh after large jobs complete, especially if generation is still in progress.
Verify your project permissions if you expected more activity than you can see.