> ## 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.
# Team Management
> Give every internal user and partner contact exactly the access they need - role-based permissions for your team, scoped access to assigned partners, and custom partner team roles.
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.
}
;
};
> As a program grows, so does the list of people who touch it. Team management lets you grant precise access to your internal team and define who manages each partner, all from clear permission categories you control without engineering.
## What it does
Team management is where you invite your internal team and assign each person a role. Roles are built
from readable permission categories, partners, commissions, courses, integrations, SSO, and more, so
you grant exactly what a person needs. You can give a user full admin access, a custom permission set,
or limit them to only the partners they are assigned.
On the partner side, you define partner team roles and assign the people responsible for each partner.
That keeps ownership clear, and because roles can map to your CRM, the right relationships stay
reflected in the system of record.
## The problem it solves
Loose access is a liability, and rigid access is a bottleneck:
* **Everyone has more access than they should** → Roles grant only the permission categories a person needs.
* **Reps see partners that are not theirs** → Users can be limited to their assigned partners.
* **Adding a teammate means an IT ticket** → Partner ops invites and assigns roles directly, no engineering.
* **Partner ownership is unclear** → Partner team roles make who-manages-whom explicit and CRM-synced.
## From problem to solution
Create roles once from the permission categories, invite your team into them, and assign partner team
roles to keep ownership clear. Access stays tight and current, and your team manages all of it without
waiting on engineering.
## Use cases
Invite teammates into the right role.
Limit users to their own partners.
Grant only the categories a role needs.
Put the right people on each partner.
## Impact
* **Low total cost of ownership** - Your team configures roles and access with no code.
* **CRM-native** - Partner team roles can map to your CRM, keeping ownership in sync.
## Who it's for
Configures roles and partner ownership.
Controls access and scoped permissions.
## Works with
{/* CONNECTS:START - generated content goes here */}
Partner team roles defined here get assigned to partners.
SSO authenticates; roles authorize.
Limit users to the partners they manage.
## Headless
## Going deeper
Setup, configuration, and all how-to guides.
Integration surface and code.