> ## 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
> One governed home for every partner-facing asset - organized, branded, embedded into the portal, and tracked for engagement.
export const Headless = ({prompts = []}) => {
const PromptRow = ({prompt}) => {
const [copied, setCopied] = useState(false);
const copy = () => {
try {
navigator.clipboard?.writeText(prompt);
} catch {}
setCopied(true);
setTimeout(() => setCopied(false), 1600);
};
return ;
};
return <>
Introw is headless by design: run everything here in plain language from Claude, ChatGPT,
Slack, Teams, or your own CRM through Introw's MCP server, with every
action written straight back to your CRM source of truth. The portal is one surface, never the only one.
{prompts.length > 0 ? :
The agentic playbook - lifecycle deep dives and a Claude Code skill library that run your partner program
from Claude, ChatGPT, Slack, and your CRM.
}
;
};
> 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.
## What this area does
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.
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.
## Why it matters
* **Time to value** - Upload what you already have and one governed library powers every surface immediately, so partners get current assets on day one instead of after a content-migration project.
* **Low total cost of ownership** - Partner marketing manages the whole library, versions, and visibility rules with no engineering.
* **Work where you already are** - Assets reach partners through the portal, share links, and CRM surfaces, so they never have to hunt for the latest deck.
* **AI-native** - AI translates documents and turns your content into partner-facing answers, so one source stays useful in every language and channel.
## How it fits together
Content is governed once, surfaced in the portal, and measured:
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
library["Asset library"] --> govern["Govern visibility"]
govern --> surface["Surface in the portal"]
surface --> track["Track engagement"]
```
## Capabilities
Store, organize, and govern every partner-facing asset in one place.
Build reusable content blocks once and reuse them across experiences.
Embed curated assets into partner portal rooms with controlled visibility.
Let partners personalize and download co-branded collateral from a template you control.
Arm partners with AI-ready, co-branded campaign assets and attribute the demand they drive.
## Who works in this area
Curates the content partners use and embeds it in the portal.
Governs visibility, folders, and access across the library.
Wants enablement that is measurable and on-brand.
## Headless
## All guides
{/* ROLLUP:START - generated content goes here */}
Embed a browsable, curated asset library in a partner experience, from adding the block to publishing it.
Embed your asset library once and use audience filters to automatically show each partner only the content relevant to their tier, phase, experience, role, or CRM data.
Add content, organize it into folders and categories, set who can see each asset, and give AI the context to answer on it.
See which assets partners view, how interest trends over time, and which partners and people engage.
Send a single asset to a partner by link, set who can open it, and see whether they viewed it.
Use asset history to see every change to an asset and roll back to any previous version in one click.
Generate language variants of a document with AI so every partner reads it in their own language.
Build a co-branded PDF, generate a personalized copy for each partner, and make them available in the portal.
Build a section once, insert it into many experiences, update it everywhere from one place, and detach a one-off when needed.
Assemble messaging, email templates, and co-branded collateral into one discoverable kit partners and their AI agents can launch from.
Wire affiliate links and end-user forms so partner-driven clicks, leads, and conversions attribute back to each partner in your CRM.