> ## 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.
# Tasks
> Assign, automate, and show the tasks that move partners through onboarding and activation in the portal.
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.
}
;
};
> Onboarding and activation only happen when someone owns the next step. Tasks give every partner a clear checklist, assigned and tracked, so nothing stalls.
## What it does
Tasks are the concrete to-dos that drive a partner forward: complete onboarding steps, finish training, submit a document, book a kickoff. You assign tasks to partners or your own team, apply **journeys** so the same playbook reaches every new partner, and automate task creation so the right tasks appear at the right moment. Partners see their tasks in the portal and check them off, and you track completion across the program.
Where Journeys describe the phases a partner moves through, Tasks are the individual actions that get them there, and both work together.
## The problem it solves
* **New partners stall without a clear next step** → Every partner gets an assigned, visible task list.
* **Onboarding is rebuilt by hand for each partner** → Journeys apply the same playbook automatically.
* **Managers chase tasks over email** → Tasks are tracked in one place with status.
* **Partners do not know what to do in the portal** → Their tasks appear right in the experience.
## From problem to solution
Instead of an onboarding plan that lives in a spreadsheet and depends on manual chasing, tasks are assigned and automated through journeys. A new partner sees exactly what to do, the manager sees who is behind, and activation becomes a repeatable motion rather than a series of reminders.
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
journey["Journey assigns tasks"] --> see["Partner sees next steps"]
see --> track["Manager tracks progress"]
track --> activate["Activation"]
```
## Use cases
Give new partners a clear, assigned checklist.
Apply journeys to every partner.
Create tasks automatically at the right moment.
See task completion across partners.
## Impact
* **Low total cost of ownership** - partner managers build and assign tasks with no code.
* **Partner self-serve** - partners see and complete their own tasks in the portal.
## Who it's for
Assigns and tracks partner tasks.
Journeys and automations for the onboarding playbook.
## Works with
{/* CONNECTS:START - generated content goes here */}
Tasks make up a journey.
Same task model on shared deals.
Show partners their tasks in the portal.
## Headless
## Going deeper
Setup, configuration, and all how-to guides.
Endpoints and code.