# Asset Library The Asset Library is a central place to store brand assets, reusable media, and source documents your team uses across content. Assets are org-scoped, so every member of your org can find the same logos, templates, documents, and generated visuals. ### What it holds * Images uploaded by your team * Generated visuals you want to keep * Reusable brand assets such as logos, headshots, product shots, icons, fonts, and templates * PDF documents that can be analysed and reused as source material * For Web3 Project orgs: structured project documents — FAQ documents, help docs, and roadmap files — surfaced as their own categories ### Safe for content Each asset has a **Safe for content** flag. Mark an asset safe when it's appropriate to attach to public posts; brand-asset pickers in the [Publishing](/thecontentforge-docs/feature-guides/publishing.md) panel only show assets that are flagged safe. Internal references, watermarked drafts, and unfinished visuals should stay unmarked. ### Ephemeral uploads When you attach a one-off image or video at publish time, it's stored as an **ephemeral** asset. Ephemeral attachments are cleaned up automatically 24 hours after the post publishes — durable brand assets in the library are not affected. ### Documents and PDFs Upload a PDF as a **document** asset to extract useful source material for content work. Document analysis runs as a background job and shows up in the [Generation Queue](/thecontentforge-docs/feature-guides/generation-queue.md) alongside Content Forge and Video Forge work, so you can keep working while it processes. The document analyser can produce: * A summary and section breakdown * Key claims and supporting details * Metrics, numbers, and named entities * Deeper insights when available * Post ideas and angles that can be used in Content Forge If only part of a PDF is processed, the document card will say so. Page, file-size, and monthly document limits depend on your plan or custom override. ### Workflow 1. Upload assets directly to the library 2. For PDFs, choose the **document** category and watch progress in the Generation Queue 3. Review the summary, claims, metrics, and ideas on the asset card 4. Mark visual assets **Safe for content** when they're cleared for public posts 5. Click **Use as source in Content Forge** to open Content Forge with the document context prefilled 6. Generate, revise, publish, or schedule the post from Content Forge Images and reusable brand assets can still be downloaded, renamed, kept for reference, and used as visual material in your publishing workflow. ### Tips * Tag and rename uploads; a generic `IMG_4827.jpg` is hard to find next month * Keep **Safe for content** strict — the brand-asset picker pulls directly from this flag * For Web3 Project orgs, file project documentation (FAQ, help, roadmap) under its dedicated category so the structured-context flows can find it * Clean out one-off uploads periodically so the library stays useful * Re-analyse a document if you raised a plan cap or want to retry deeper extraction --- # Agent Instructions: 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: ``` GET https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/asset-library.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.