> ## 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 Team
> Assign your team to each partner with clear roles, and let that ownership drive who appears in the portal, who sends partner communications, who issues certificates, and who approves submissions.
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 relationship needs an owner. Assigning your team to each partner makes ownership explicit, and that one decision drives the experience: who the partner sees as their contact, who signs their communications, who approves their requests, and who issues their certificates.
## What it does
Partner Team is where you put the right people from your side on each partner. You assign team members to a partner and give them a role, such as the lead partner manager, a co-owner, or a technical contact. That assignment is not just a label: it cascades through the rest of the program so partner-facing surfaces reflect the real human relationship.
Once a partner has an assigned team, Introw uses it everywhere it matters. The portal can show the partner their points of contact, kept current automatically as assignments change. Partner-facing announcements and emails can be sent from and replied to the assigned manager instead of a generic address. Certificates can carry the assigned manager as their issuer. Form approval workflows can route to the partnership manager rather than a hard-coded name. And because partner team roles can map to a CRM property, ownership stays reflected in your system of record.
The mechanics of building roles and scoping access live in [Team Management](/features/access/team-management). Partner Team is the partners-domain view of the same idea: who owns this partner, and what that ownership unlocks.
## The problem it solves
* **Partners do not know who their contact is** → The portal shows their assigned points of contact, kept current automatically.
* **Communications come from a faceless address** → Announcements and emails are sent from the assigned manager, so partners reply to a real person.
* **Approvals and certificates name a person who has left** → Workflows route to the partnership manager role and credentials carry the current issuer, not a hard-coded name.
* **Ownership is unclear and drifts from the CRM** → Partner team roles make who-owns-whom explicit and can sync to a CRM property.
## From problem to solution
Assign each partner a team once, with roles that mean something. From that point the relationship is wired through the product: the partner sees a face, hears from a person, gets approvals from the right desk, and earns certificates with a real signatory, all without you re-entering names on each surface.
## Use cases
Assign the lead manager and supporting roles per partner.
Show partners their points of contact automatically.
Send announcements and emails from the assigned manager.
Send form approvals to the partnership manager role.
## Impact
* **Low total cost of ownership** - partner ops assigns teams and roles with no code, and every downstream surface follows.
* **CRM-native** - partner team roles can map to a CRM property, keeping ownership in sync with your source of truth.
## Who it's for
Owns the partners assigned to them and appears as their contact.
Defines roles and keeps partner ownership clean and CRM-synced.
## Works with
{/* CONNECTS:START - generated content goes here */}
Roles are defined in team management.
Show points of contact in the portal.
Route approvals to the assigned manager.
Issue certificates as the assigned manager.
## Headless
## Going deeper
Setup, configuration, and all how-to guides.
Endpoints and code.