> ## 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 Portal & Branding
> Launch a personalized, white-labeled partner portal on your own domain - built no-code, branded as yours, and used to announce what matters.
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.
}
;
};
> Partner Portal & Branding is how you give partners a home that looks like you: a no-code portal experience, branded end to end, served on your own domain, with announcements that reach partners wherever they are.
## What this area does
A partner portal should feel like an extension of your brand, not a generic tool partners tolerate. This area lets your team build that portal without engineering. You design experiences from sections and stages, brand every surface with your colors, fonts, and logos, and serve the whole thing on your own custom domain so partners never see someone else's name.
Getting partners in and keeping them informed is part of the same story. You decide how partners log in and who can see what, invite the right people, and broadcast announcements that land in the portal, by email, and in Slack or Teams. Because Introw is built to meet partners off-portal too, the portal is the polished home base while updates still reach partners where they already work.
## Why it matters
* **Low total cost of ownership** - Partner marketing and ops build and brand the entire portal with no-code, never waiting on engineering.
* **Time to value** - Launch a branded portal on your own domain in minutes, not a multi-month implementation.
* **Work where you already are** - Announcements reach partners in the portal and beyond it, by email and in Slack or Teams.
## How it fits together
A branded portal goes from build to live partners on your own domain:
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
build["Build experience"] --> brand["Brand it"]
brand --> domain["Serve on your domain"]
domain --> access["Partners get access"]
access --> announce["Announcements reach them"]
```
## Capabilities
Build the portal no-code from stages, sections, and blocks, and publish it to partners.
Apply your colors, fonts, and logos across the portal, emails, and reports.
Serve the partner portal on your own domain with verified DNS.
Send partner notifications from your own authenticated domain.
Decide how partners log in, who gets access, and what each segment can see.
Broadcast updates to partners in the portal, by email, and in Slack or Teams.
Publish a searchable directory of your partners, composed from partner data, forms, and the API.
Let partners install and use the portal as an app on their phone.
## Who works in this area
Builds and brands the portal and runs announcements to keep partners engaged.
Configures access, domains, and login so the right partners get in safely.
Wants a credible, branded partner experience live fast.
## Headless
## All guides
{/* ROLLUP:START - generated content goes here */}
Draft a partner announcement in seconds from a URL or prompt using an AI preset, then refine and send it.
See who an announcement was sent to, who opened it, and who clicked, then decide who to nudge.
Compose an announcement, set who it comes from and who handles replies, target the right segments, choose channels, and publish or nudge.
Make the emails partners receive carry your logo and colors so off-portal messages still look like your product.
Apply your logos, colors, font, and login copy so the portal, login screen, and experiences all look like your product.
Add your hostname, create the DNS records it generates, and verify so the partner portal serves securely on your own domain.
Disconnect a custom domain so the portal falls back to its default address without locking partners out.
Set your sender, add the DNS records Introw generates, and verify so partner notifications send from your own authenticated address instead of the default Introw one.
Show each logged-in partner their own details, tier, and key information inside a portal experience.
Create an experience, structure it into stages, fill it with sections and calls to action, then assign it to partners and publish.
Embed documents, videos, and meeting schedulers from the providers Introw supports directly inside a portal experience.
Use experience history to review every change to a partner portal experience and roll back to a previous version in one click.
Add the partner portal to a phone home screen.
Find deals, content, and commissions on a phone.
Assemble a partner directory from Introw's building blocks: partner-maintained profiles via forms, an in-portal profile section, a public listing from the partners API, and a take-in form that auto-attributes buyer demand to the right partner.
Let one partner contact reach more than one portal with a single login across a multi-portal program.
Invite specific partner contacts into a portal, then let trusted partners bring in their own teammates.
Show a portal tab only to the partner segments it is meant for, so one portal serves different partner types.
Choose how partners sign in, decide whether access is by invite or by email domain, and handle email verification.