> ## 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.
# Partner Onboarding
> Onboard partners progressively: start them small, then unlock tabs, assets, and abilities as they complete steps and qualify, so they grow into their portal instead of drowning in it on day one.
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.
}
;
};
> A partner who lands in a portal full of everything on day one is overwhelmed and does nothing. Progressive onboarding starts them with the essentials and unlocks more, tabs, assets, and abilities, as they complete steps and qualify, so the portal grows with them.
## What it does
Partner Onboarding is a way of designing the partner experience so it reveals itself over time. Instead of exposing the full portal to a brand-new partner, you start them with a focused first stage, the few things they need to get going, and let the rest unlock as they earn it. Finish onboarding tasks, pass a certification, reach a tier, or hit a CRM milestone, and new tabs, content, and abilities appear.
This is built by combining what is already in Partners and the Portal. Dynamic segments decide who has reached each stage and update themselves as partner data changes. Portal experiences restrict tabs and sections to those segments, so a partner only sees what they have unlocked. Journeys give them the checklist that drives them forward, and tiers and certificates provide the milestones that flip the switch. The result is a partner who is never lost, always has a clear next step, and feels the program open up as they grow.
Because everything keys off live segment membership, the unlocking is automatic. You design the path once; partners move through it on their own, and you spend your time on the ones who stall, not on manually granting access. And because a partner's segments always resolve to the most permissive settings, every stage they earn only ever adds: nothing a partner unlocked gets taken away by still matching an earlier stage.
## The problem it solves
* **New partners are overwhelmed by a full portal** → Start them with a focused first stage and reveal the rest over time.
* **Access is granted by hand, partner by partner** → Dynamic segments unlock tabs and assets automatically as partners qualify.
* **Partners plateau with nothing pulling them forward** → Each unlock is a reward tied to a completed step or milestone.
* **There is no defined path to productive** → Onboarding becomes a designed progression, not a pile of links.
## From problem to solution
Design the stages of your onboarding, define a dynamic segment for each, and gate the matching portal tabs, assets, and abilities to those segments. Partners start small, complete the steps in front of them, and watch the portal expand as they qualify, turning onboarding into a guided climb instead of a cliff.
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
stages["Design stages"] --> segments["Segment per stage"]
segments --> gate["Gate portal tabs and assets"]
gate --> unlock["Portal unlocks as partner qualifies"]
```
## Use cases
Reveal tabs as partners reach each stage.
Unlock assets and abilities when partners qualify.
Let dynamic segments grant access, not your inbox.
Give a clear next step from day one to productive.
## Impact
* **Time to value** - partners reach productive faster because the path is staged and clear.
* **Partner self-serve** - partners unlock the program on their own as they qualify.
* **Low total cost of ownership** - partner ops designs the progression with no-code segments and experiences.
## Who it's for
Wants new partners productive without hand-holding.
Designs the staged content and unlocks.
## Works with
{/* CONNECTS:START - generated content goes here */}
Unlock stages with dynamic segments.
Give partners the onboarding checklist.
Reveal portal tabs as partners qualify.
## Headless
## Going deeper
Setup, configuration, and all how-to guides.
Endpoints and code.