The Assets Hub lives on the company-specific route pattern /companies/[id]/assets.

Use the Assets Hub when you want to:

The empty state makes the purpose clear. When there are no assets yet, the page says the library is quiet for now and explains that the starter pack lands there automatically after onboarding. It also tells the user that they can upload sources or run a custom draft while they wait, or grab deliverables from tasks as they ship. That is the right mental model for the hub: onboarding creates the first documents, tasks feed new deliverables into the library, and the hub stores the ongoing record.

The starter pack is part of the onboarding flow, not a separate thing the user has to remember to trigger from the hub. When starter assets are finished, the page shows a banner that says Starter kit ready and explains that Business Profile, Growth Brief, and checklist are in your library below.

While the starter documents are still building, the banner changes state:

The important support note here is that the page does not ask the customer to guess what happened. It either shows that the starter documents are still working, or it tells them the kit is ready, or it clearly flags a failure state that needs support.

The hub's type picker includes four visible choices:

That list matches the asset types surfaced in the page UI. It is useful to keep the explanation anchored to those names, because customers will see the same terms in the dropdowns and in the generated items.

The most important distinction is between the built-in starter documents and user-triggered generation:

If a customer asks whether the hub can create everything on demand, be careful. The page does expose starter-document types in the selector, but the actual product story is still that onboarding creates the starter pack automatically and tasks promote deliverables into the library. The hub is the place where those results live.

The page gives the customer a few direct ways to work with the library:

The page also shows a Workspace Usage card with four measurements that matter for support:

That card also shows Upload Max, which is the maximum single upload size for the workspace. If a customer cannot upload a file, this is the first place to check because the page will surface the cap before the upload fails.

The list view is built around the asset lifecycle, and the page exposes the statuses customers will actually see:

The filter controls also include All Types and All statuses, so support can tell a customer to start there if the list looks empty or crowded. The page text will also tell the user when every item is already in view by saying All statuses in view.

This matters because assets are not static files. They move through a lifecycle, and the list is trying to help the customer understand which items are still editable, which are waiting on review, which are stale, and which ones have been superseded by newer evidence.

If a generation job is running, the progress card shows the live state. The UI uses the states Waiting in queue, Generating content, Done, and Stopped, and the action button changes from Open document to Open first document when there are multiple starter outputs. That is useful when support needs to explain why a result is not visible yet.

When a source document is uploaded, the page confirms that the document was uploaded and queued for learning. This is a good phrase to reuse in chat because it reflects the actual behavior of the page: uploads are not just stored, they are also sent into the learning pipeline.

Keep the explanation grounded in the real UI:

The safer explanation is that the Assets Hub is the company workspace's durable document library. It contains starter content, task deliverables, custom drafts, and uploaded sources, while showing quota and lifecycle state so the user knows what is possible right now.

Direct the customer here when they ask about:

If they only need to edit a single asset, use the asset detail route pattern /companies/[id]/assets/[assetId]. If they want the full library view, use the Assets Hub.

If something does not look right, confirm you are using the correct account, page, and permission level.