> ## 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.
# Asset Library
> One governed home for every partner-facing asset - organized, access-controlled, multilingual, 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.
}
;
};
> The Asset Library is the single source of truth for partner content: every file, link, and embed in one place, with the right partners seeing the right thing and a clear view of what they actually use.
## What it does
The Asset Library holds everything partners need: documents, presentations, links, and embeds,
organized into folders and tagged with categories. You upload or import content once and manage
it centrally, so partners always reach the current version instead of a stale copy floating in
someone's inbox. Visibility controls let you decide per asset whether it is public, portal-only,
or restricted to specific segments.
The library is built for partner enablement at scale. You can generate language variants of
documents so partners read content in their own language, produce co-branded versions for
partners to use, and track engagement to see which assets get viewed. Because the same library
feeds the portal, share links, and CRM surfaces, your content reaches partners wherever they
work.
## The problem it solves
Scattered, stale content is the quiet killer of partner enablement:
* **Content lives in too many places** → Store every asset in one governed library.
* **Partners get stale versions** → Manage one source of truth that always serves the current file.
* **Everyone sees everything, or nothing** → Set visibility per asset across public, portal, and restricted.
* **Partners need content in their language** → Generate language variants with AI.
* **You cannot tell what content works** → Track which assets partners view.
## From problem to solution
The Asset Library turns content chaos into a governed system. Organize once, control visibility,
localize with AI, and watch engagement. Enablement becomes a managed, measurable program instead
of a pile of files nobody can find.
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
organize["Add and organize"] --> govern["Control visibility"]
govern --> localize["Localize with AI"]
localize --> track["Track engagement"]
```
## Use cases
Keep every asset in one organized, current library.
Decide who sees each asset, from public to segment-restricted.
Generate language variants so partners read in their language.
See which assets partners actually use.
## Impact
* **Time to value** - Upload what you already have and it powers every partner-facing surface immediately, with nothing to migrate.
* **Low total cost of ownership** - Partner marketing runs the full library, no engineering.
* **AI-native** - AI translates documents and powers content-based partner answers.
## Who it's for
Curates and localizes the content partners use.
Governs folders, categories, and access.
## Works with
{/* CONNECTS:START - generated content goes here */}
Assets surface in portal experiences.
Co-brand assets from the library.
Reuse library content in synced sections.
## Headless
## Going deeper
Setup, configuration, and all how-to guides.
Integration surface and code.