> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/create-and-publish/production/content-hub/organize-generated-content.md).

# Organize generated content

Find generated content in Catalog and Content Packs, set its status, and track output on the Dashboard.

Use this task to find and organize everything that Content Hub generates. Every text, clip, and quote is an asset. Content Hub groups assets in content packs per episode, lists them in the Catalog, and counts them on the Dashboard. Each asset has the status **Draft**, **Ready**, or **Archived**.

## Before you start

* You need Content Hub access. See [Get started with Content Hub](/documentation/create-and-publish/production/content-hub/get-started-with-content-hub.md).
* Generate at least one asset, for example with [Generate text content from an episode](/documentation/create-and-publish/production/content-hub/generate-text-content-from-an-episode.md).

{% tabs %}
{% tab title="Classic view" %}

### Review one episode in its content pack

1. In the sidebar, select **Content Packs**. The list shows **Episode**, **Podcast**, **Assets**, and **Updated** for each pack, 20 packs per page.
2. Optional: filter by podcast or search by episode title.
3. Open the pack to see every asset created from that episode.

Each episode gets one pack. Podigee creates the pack when you save the first asset for the episode, and also when you publish an episode. Assets without an episode, for example an Ask Podie draft, go into a pack of the podcast. Until the first pack exists, the page shows **No content packs yet**.

### Find any asset in the Catalog

1. In the sidebar, select **Catalog**.
2. Switch between the **Table** and **Grid** views. The table shows **Type**, **Title**, **Source**, **Status**, and **Updated**.
3. Filter by status (**Draft**, **Ready**, **Archived**), format (**Video**, **Audio**, **Text**, **Image**, **Document**), platform, or podcast.
4. Enter text in **Search** to search titles and text.
5. Open an asset in the **Asset Preview** to see its **Duration** and **Platform**.

The Catalog shows 20 assets per page, newest update first. If the filters match nothing, the page shows **No assets match your filters.**

![Catalog in the classic view with the Table and Grid switch, the filters Status, Format, Platform, and Podcast, the Search field, and the empty state No content yet](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-a9269856e1389d500840e73306d250206c797189%2Fdoc-production-020-classic-catalog.png?alt=media)

The Catalog filters every asset by status, format, platform, and podcast, and switches between Table and Grid.

### Change the status of an asset

* **Approve** sets the status to **Ready**. The page shows **Asset marked as ready.**
* Archive an asset to set the status to **Archived**. The page shows **Asset archived.**
* Edit the title (up to 255 characters) or the body from any listing. The page shows **Asset updated.**

Quotes from Quote Finder are **Ready** as soon as you save them. You cannot approve an asset while its generation runs. The page shows **This asset is currently being generated. Please wait until it is finished.**

### Track your output on the Dashboard

1. In the sidebar, select **Dashboard**.
2. Read the counters:
   * **Packs**: content packs, one per episode.
   * **Assets**: individual pieces of content such as blog posts, clips, and quotes.
   * **Drafts**: assets still being edited.
   * **Ready**: assets marked as ready for publishing or sharing.
3. Read the Ask Podie panel. **Indexed** shows how much of your podcast library is searchable. **Assets (30d)** and **Episodes Used** show the recent output. **Time Saved** shows an estimate that is based on the average time to create content manually.

Before the first asset exists, the Dashboard shows **Get started with Content Hub** and **Create your first content**.

![Content Hub Dashboard in the classic view with the counters Packs, Assets, Drafts, and Ready, the Get started with Content Hub card, and the Ask Podie panel](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-fa416534c2a0b7622098e5459ea5aefd067f492a%2Fdoc-production-020-classic-dashboard.png?alt=media)

The Dashboard counts packs, assets, drafts, and ready assets and shows the Ask Podie panel below the counters.

### Expected result

You can open any generated asset from its content pack or from the Catalog. Its status tells your team if the asset is still in work, ready to publish, or archived.

### If you cannot complete the task

* An asset is missing from the Catalog: check the status filter. The Catalog hides archived assets when you filter for **Draft** or **Ready**.
* A pack shows fewer assets than expected: deleted assets no longer count.
* The Dashboard counters look old: Podigee refreshes the counters at intervals. Reload the page later.
  {% endtab %}

{% tab title="Podigee workspace" %}
The Podigee workspace does not include the Catalog, content packs, or the Content Hub dashboard yet. Switch to the classic view to organize generated content.
{% endtab %}
{% endtabs %}

## Next step

[Set brand guardrails](/documentation/create-and-publish/production/content-hub/set-brand-guardrails.md) improves every future generation. Agents can list and inspect the same assets. See [Find generated content assets](/documentation/start-here/ai-agents/search-and-repurpose-episode-content/find-generated-content-assets.md) and [Understand content asset types and states](/documentation/start-here/ai-agents/search-and-repurpose-episode-content/understand-content-asset-types-and-states.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/create-and-publish/production/content-hub/organize-generated-content.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
