> ## 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.

# Content & Enablement

> Manage every partner-facing asset in one place - organized, co-branded, embedded into the partner portal, and tracked for engagement across partners.

export const Headless = ({children, intro = true}) => {
  const [copied, setCopied] = useState(null);
  const copy = event => {
    const row = event.target.closest("li");
    if (!row) return;
    const text = row.textContent.trim();
    try {
      navigator.clipboard?.writeText(text);
    } catch {}
    setCopied(text);
    setTimeout(() => setCopied(null), 1600);
  };
  return <>
      {intro ? <p>
          Introw is <strong>headless</strong> by design: run everything here in plain language from Claude, ChatGPT,
          Slack, Teams, or your own CRM through Introw's <a href="/features/developer/mcp">MCP server</a>, with every
          action written straight back to your CRM source of truth. The portal is one surface, never the only one.
        </p> : null}

      {children ? <div className="not-prose" data-prompts="block">
          <div data-prompts="head">
            <span>{copied ? "Copied" : "Try it from your LLM"}</span>
          </div>
          <div data-prompts="rows" onClick={copy}>
            {children}
          </div>
          <a href="/headless/prompts" data-prompts="more">
            See all prompts
          </a>
        </div> : <Card title="See the headless motion" icon="wand-magic-sparkles" href="/headless">
          The agentic motion - lifecycle deep dives and a Claude Code skill library that run your partner program from
          Claude, ChatGPT, Slack, and your CRM.
        </Card>}
    </>;
};

export const Rail = ({children}) => <div className="not-prose" data-overview="rail">
    {children}
  </div>;

export const Impact = ({children}) => <div className="not-prose" data-overview="impact">
    {children}
  </div>;

export const Personas = ({children}) => <div className="not-prose" data-overview="personas">
    {children}
  </div>;

export const Pains = ({children}) => <div className="not-prose" data-overview="pains">
    {children}
  </div>;

> Content & Enablement is the central, governed library behind every partner-facing surface: store and organize assets once, control who sees what, embed them into the portal, and see what partners actually use.

## The problem it solves

<Pains>
  | Without Introw | With Introw |
  | - | - |
  | Content is scattered across drives | One governed library |
  | Partners get the stale version | One source, always current |
  | Everyone sees everything, or nothing | Visibility set per asset |
  | You cannot tell what gets used | Views tracked per asset |
</Pains>

## Impact

Partners sell with whatever is easiest to find. Being the vendor whose current, co-branded, on-brand material is one click away in their own portal is how you get sold.

<Impact>
  for your business

  * **Live in days**
    Upload what you already have and it powers every partner surface immediately, with no content migration first
  * **Cost to run**
    Partner marketing runs the library, its versions and its visibility rules without engineering
  * **AI, not admin**
    AI translates documents into partner languages, and your decks and docs become the answers the agents give

  for your partners

  * **Self-serve**
    They browse and search a curated hub in their own portal, instead of asking for the latest deck
  * **Enabled**
    Co-branded templates open as their own version, ready to use, with no design request to raise
  * **Efficient**
    Office files open in the browser with nothing to download, in their own language

  [A day in the life of a reseller](/days-in-the-life/reseller)
</Impact>

<Personas>
  * **Partner Marketing** - one library behind every surface
  * **Partner Operations** - visibility governed in one place
  * **VP Partnerships** - enablement you can measure
  * **Partners** - current material, one click away
</Personas>

## How this area works

Partner enablement falls apart when content is scattered across drives, decks, and email threads. This area gives you one home for every asset partners need: upload files, add links and embeds, organize them into folders and categories, and serve the same governed content everywhere. You control visibility per asset, from fully public to portal-only to segment- restricted, and you keep one source of truth instead of stale copies.

Content is governed once, surfaced in the portal, and measured.

**Where this sits in a setup.** Content is what makes a portal worth opening twice. The [co-sell](/tracks/co-sell) and [reseller](/tracks/reseller) tracks bring it in once the portal is live rather than before.

<Rail>
  * ![An asset open beside the library, with its type, view count, portal access, categories and languages, and the tabs for access, languages, engagement and history.](https://assets.introw.io/docs/features/content/asset-library/shots/asset.png)

    [**Asset Library**](./asset-library)

    Every file, link and embed, governed in one place.

    [How to · 6 guides](./asset-library/technical)

  * ![The Synced sections tab beside Experiences, the shelf reusable blocks are saved to and dropped into any experience from.](https://assets.introw.io/docs/features/content/synced-sections/shots/library.png)

    [**Synced Sections**](./synced-sections)

    One block, reused across every experience.

    [How to · 1 guide](./synced-sections/technical)

  * ![The Documents & videos tab of a portal experience, the asset hub partners browse, configured in the experience builder.](https://assets.introw.io/docs/features/content/asset-hub/shots/hub.png)

    [**Asset Hub**](./asset-hub)

    A curated, searchable hub inside the portal.

    [How to · 2 guides](./asset-hub/technical)

  * ![A document asset open in the library, where co-branding replaces the placeholders with each partner's own details before download.](https://assets.introw.io/docs/features/content/co-branded-assets/shots/cobrand.png)

    [**Co-branded Assets**](./co-branded-assets)

    One template, and each partner opens their own.

    [How to · 1 guide](./co-branded-assets/technical)

  * ![The Campaign kits hub in a partner's portal, six assets as matching thumbnails with their descriptions and the Q4 2026 campaign category.](https://assets.introw.io/docs/features/tcma/campaign-kits/guides/enable-partners-with-a-campaign-kit/steps/23.png)

    [**Through-Channel Marketing**](/features/tcma)

    Turn a folder of assets into a campaign kit partners launch, with ROI per campaign.

    [How to · 2 guides](/features/tcma/campaign-kits/technical)
</Rail>

From that library, you build reusable content blocks and surface assets in the partner portal. Synced sections let you maintain a block once and reuse it across experiences, and Asset Hub embeds put curated assets directly in partner portals. Engagement tracking then shows which assets partners view, so enablement becomes something you measure and improve rather than guess at. AI helps along the way, from translating documents to powering partner-facing answers from your content.

Content is governed once, surfaced in the portal, and measured.

## Run it from your AI assistant

<Headless>
  * Which assets are partners viewing most this month?
  * Has Acme opened the latest pricing deck?
</Headless>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.