> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Build the asset library

> Add content, organize it into folders and categories, set who can see each asset, and give AI the context to answer on it.

> For partner marketing and partner ops standing up the content library partners actually use.

A content library only delivers value when partners can find the right asset and only the people who should see it can. This guide covers the whole setup: adding content, structuring it into folders and categories, setting visibility per asset, and giving AI the context to answer partner questions from your content. Do it once and every downstream surface, hubs, experiences, and share links, draws from a clean, governed library.

## What you'll achieve

A structured library where assets live in clear folders, are tagged for filtering, carry the right access level, and are ready to surface anywhere in the portal. Public collateral stays open, sensitive material is limited to the portal or specific segments, and AI can answer partner questions accurately from the content you added.

## Before you start

<Steps>
  <Step title="Confirm write access">
    You need write access to assets to add and manage content.
  </Step>

  <Step title="Define segments if restricting access">
    If you plan to restrict any asset to specific partners, create those segments first so they are ready to apply. See [Create a dynamic segment](/features/partners/segments/guides/create-a-dynamic-segment).
  </Step>
</Steps>

## Watch it

<Tabs>
  <Tab title="Video">
    <video controls playsInline preload="none" poster="https://assets.introw.io/docs/features/content/asset-library/guides/build-the-asset-library/steps/02.png?v=1783348841" className="w-full rounded-xl" src="https://assets.introw.io/docs/features/content/asset-library/guides/build-the-asset-library/video.webm?v=1783348841#t=2.5" />
  </Tab>

  <Tab title="Click through">
    <iframe className="w-full rounded-xl" style={{ width: "100%", aspectRatio: "16 / 11", border: 0, backgroundColor: "#FAFAFA" }} src="https://assets.introw.io/docs/features/content/asset-library/guides/build-the-asset-library/walkthrough.html?v=1783348841" />
  </Tab>
</Tabs>

## Steps

### Add and organize content

<Steps>
  <Step title="Open Assets">
    Go to [Assets](https://app.introw.io/assets/library), the home of your content library.

    <Frame>
      <img src="https://assets.introw.io/docs/features/content/asset-library/guides/build-the-asset-library/steps/02.png?v=1783348841" alt="Open Assets" />
    </Frame>
  </Step>

  <Step title="Create folders that match how partners think">
    Build a folder structure before bulk-loading content, so assets land in the right place. Name folders the way partners search, for example by product, use case, or stage. Folders can be nested, and they are what hubs include or exclude later, so a clean structure pays off across the portal.

    <Frame>
      <img src="https://assets.introw.io/docs/features/content/asset-library/guides/build-the-asset-library/steps/03.png?v=1783348841" alt="Create folders that match how partners think" />
    </Frame>
  </Step>

  <Step title="Add content">
    Use the add menu to bring content in. Choose the type that fits the source:

    * **Upload a file** - add a document, slide deck, image, or PDF stored as a file. Use this for collateral you own and want hosted in Introw.
    * **Import a folder** - bring in a whole folder tree at once, from a chosen folder or a ZIP. Optionally keep it syncing from its source so the library stays current as the source changes; turn syncing on when the content is maintained elsewhere.
    * **Add a web page URL** - add a link or an embed for hosted content such as a video or a Google document. Introw recognises common providers and embeds them inline rather than linking out.

    <Frame>
      <img src="https://assets.introw.io/docs/features/content/asset-library/guides/build-the-asset-library/steps/04.png?v=1783348841" alt="Add content" />
    </Frame>
  </Step>

  <Step title="Tag assets with categories">
    Add categories to assets so they can be filtered across the library and inside Asset Hub embeds. Categories act as shared, filterable tags, so use a consistent, small set rather than free-form labels on every asset.

    <Frame>
      <img src="https://assets.introw.io/docs/features/content/asset-library/guides/build-the-asset-library/steps/05.png?v=1783348841" alt="Tag assets with categories" />
    </Frame>
  </Step>
</Steps>

### Set who can see each asset

<Steps>
  <Step title="Open the Access tab">
    Open an asset and go to its **Access** tab. Access is set per asset, so you can keep public collateral open while locking sensitive material down.

    <Frame>
      <img src="https://assets.introw.io/docs/features/content/asset-library/guides/build-the-asset-library/steps/06.png?v=1783348841" alt="Open the Access tab" />
    </Frame>
  </Step>

  <Step title="Choose an access level">
    Pick the level that matches the sensitivity of the asset:

    * **Public access** - anyone with the link can view the asset. Use for openly shareable collateral such as brochures.
    * **Portal access** - only partner users with portal access can view it. Use for standard enablement meant for your partners but not the public.
    * **Restricted access** - only a subset of partner users can view it. Choose this for sensitive material, then add the segments that should have access in the **Segments** selector. Restricted access depends on accurate segments, so confirm them before relying on it.

    <Frame>
      <img src="https://assets.introw.io/docs/features/content/asset-library/guides/build-the-asset-library/steps/07.png?v=1783348841" alt="Choose an access level" />
    </Frame>
  </Step>
</Steps>

### Give AI the context to answer

<Steps>
  <Step title="Open the AI tab">
    Open an asset and go to its **AI** tab. What you add here helps AI features answer partner questions accurately from this asset.
  </Step>

  <Step title="Add context and supporting files">
    Provide the background AI needs so its answers are grounded in your content:

    * **Context description** - a plain-text or Markdown note describing what the asset is and when it applies. Use it to give AI background the file itself does not spell out, so answers are accurate.
    * **Supporting files** - upload PDF, TXT, or MD files that are indexed alongside the asset to improve AI answers about it. Add reference material that complements the main asset.
  </Step>
</Steps>

## Verify it worked

Assets appear in their folders and can be filtered by category. Each asset's **Access** tab reflects the level you set, and a restricted asset is visible only to partners in the chosen segments. With AI context added, AI features can answer partner questions using that content. The library is now ready to surface in hubs, experiences, and share links.

## Related

<CardGroup cols={2}>
  <Card title="Share an asset with a link" icon="book-open" href="./share-an-asset-with-a-link">
    Send a trackable link to a single asset.
  </Card>

  <Card title="Translate a document" icon="book-open" href="./translate-a-document">
    Add language variants for a global partner base.
  </Card>

  <Card title="Add an Asset Hub" icon="book-open" href="/features/content/asset-hub/guides/add-and-configure-an-asset-hub">
    Surface library assets in a partner portal.
  </Card>

  <Card title="Implementation reference" icon="screwdriver-wrench" href="../technical">
    Full asset library configuration options.
  </Card>
</CardGroup>
