> ## 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 personalized for every partner.

export const Headless = ({children, intro = true}) => {
  const [copied, setCopied] = useState(null);
  const copy = event => {
    const row = event.target.closest("li");
    if (!row) return;
    const text = row.textContent.trim();
    try {
      navigator.clipboard?.writeText(text);
    } catch {}
    setCopied(text);
    setTimeout(() => setCopied(null), 1600);
  };
  return <>
      {intro ? <p>
          Introw is <strong>headless</strong> by design: run everything here in plain language from Claude, ChatGPT,
          Slack, Teams, or your own CRM through Introw's <a href="/features/developer/mcp">MCP server</a>, with every
          action written straight back to your CRM source of truth. The portal is one surface, never the only one.
        </p> : null}

      {children ? <div className="not-prose" data-prompts="block">
          <div data-prompts="head">
            <span>{copied ? "Copied" : "Try it from your LLM"}</span>
          </div>
          <div data-prompts="rows" onClick={copy}>
            {children}
          </div>
          <a href="/headless/prompts" data-prompts="more">
            See all prompts
          </a>
        </div> : <Card title="See the headless motion" icon="wand-magic-sparkles" href="/headless">
          The agentic motion - lifecycle deep dives and a Claude Code skill library that run your partner program from
          Claude, ChatGPT, Slack, and your CRM.
        </Card>}
    </>;
};

export const Rail = ({children}) => <div className="not-prose" data-overview="rail">
    {children}
  </div>;

export const Impact = ({children}) => <div className="not-prose" data-overview="impact">
    {children}
  </div>;

export const Personas = ({children}) => <div className="not-prose" data-overview="personas">
    {children}
  </div>;

export const Pains = ({children}) => <div className="not-prose" data-overview="pains">
    {children}
  </div>;

> 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.

## The problem it solves

<Pains>
  | Without Introw | With Introw |
  | - | - |
  | The portal looks like someone else | Your brand, down to the URL |
  | Changing it needs engineering | Partner marketing builds it |
  | Partners will not live in a portal | It reaches them off-portal too |
  | Getting people in is manual | Invite, or a trusted domain |
</Pains>

## Impact

A portal carrying someone else's name tells a partner how much the program matters to you. Yours, on your domain, from the login screen onwards, is the cheapest credibility available.

<Impact>
  for your business

  * **Cost to run**
    Partner marketing and ops build and brand the whole portal with no code, and never wait on engineering
  * **Live in days**
    A branded portal on your own domain goes live in minutes rather than after a multi-month implementation
  * **No new tool**
    The portal is the polished home base, but updates still reach partners in their inbox and chat

  for your partners

  * **Self-serve**
    They sign in the way they already do, and see only the tabs their segment has earned
  * **Enabled**
    One home that looks like your product, so it reads as part of the relationship rather than a tool
  * **Efficient**
    It works on a phone and installs to the home screen, so a deal can be registered at an event

  [A day in the life of your partners](/days-in-the-life)
</Impact>

<Personas>
  * **Partner Marketing** - the portal they own and evolve
  * **Partner Operations** - access, domains and login
  * **VP Partnerships** - a credible portal, live fast
  * **Partners** - a home that looks like you
</Personas>

## How this area works

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. Set your company domain and Introw reads your website for your logos, accent colors, and favicon ([Branding](./branding)), so the portal looks like your marketing site, not your back office, before you change anything.

A branded portal goes from build to live partners on your own domain.

**Where this sits in a setup.** The portal is the step that takes longest in every [setup track](/tracks), and the one worth starting from a minimum viable version: a pipeline, one form, one asset folder, then widen.

<Rail>
  * ![The experience builder, with the portal's tabs across the top and the sections on the home tab arranged in the order partners see them.](https://assets.introw.io/docs/features/portal/experiences/shots/builder.png)

    [**Experiences**](./experiences)

    Stages, sections and blocks, with no code.

    [How to · 4 guides](./experiences/technical)

  * ![Portal settings, with the brand colours, logo and font on the left and the partner's own sign-in screen rendering live beside them.](https://assets.introw.io/docs/features/portal/branding/shots/branding.png)

    [**Branding & White-label**](./branding)

    Apply your colors, fonts, and logos across the portal, emails, and reports.

    [How to · 2 guides](./branding/technical)

  * ![The portal domain configuration, where the default introw.io address is replaced with a domain of your own.](https://assets.introw.io/docs/features/portal/custom-domains/shots/domain.png)

    [**Custom Domains**](./custom-domains)

    The portal on your own hostname.

    [How to · 2 guides](./custom-domains/technical)

  * ![The email domain configuration, where partner notifications are sent from your own sending domain instead of Introw's.](https://assets.introw.io/docs/features/portal/email-domain/shots/email.png)

    [**Email Domain**](./email-domain)

    Notifications from your own authenticated domain.

    [How to · 1 guide](./email-domain/technical)

  * ![The login section of Portal settings, choosing how partners sign in - Google, Microsoft or a verification code - and what happens when someone has no access yet.](https://assets.introw.io/docs/features/portal/portal-access/shots/login.png)

    [**Portal Access**](./portal-access)

    How partners log in, and what they see.

    [How to · 4 guides](./portal-access/technical)

  * ![The Partners list, the directory every partner record is reached from, with the columns and saved views a team works it through.](https://assets.introw.io/docs/features/portal/partner-directory/shots/directory.png)

    [**Partner Directory**](./partner-directory)

    Publish a searchable directory of your partners, composed from partner data, forms, and the API.

    [How to · 1 guide](./partner-directory/technical)

  * ![The partner portal on a phone-width screen, with the same tabs, news and tasks reflowed into a single column.](https://assets.introw.io/docs/features/portal/mobile/shots/home.png)

    [**Mobile**](./mobile)

    Let partners install and use the portal as an app on their phone.

    [How to · 2 guides](./mobile/technical)
</Rail>

Getting partners in is part of the same story. You decide how partners log in and who can see what, and invite the right people. 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.

## One portal per motion, personalized per person

A reseller, a referral partner, and an implementation partner do not need the same portal, and at the same reseller, the technical contact does not need the same portal as the commercial lead. Introw builds each motion as its own experience and then personalizes inside it. [Segments](/features/partners/segments) decide which tabs, assets, courses, and forms a partner or a contact reaches, [tiers](/features/partners/tiers) decide what they have earned, and [progressive onboarding](/features/partners/onboarding) reveals the rest as they qualify. Two people at the same partner can sign in to genuinely different portals, one leading with spec sheets and technical courses, the other with deal registration and case studies, without you running two programs.

## The rules you set here apply everywhere

The portal is also where the partner experience is defined for every other surface. What a partner may see, submit, and act on is set once, and the shared Slack or Teams channel, the deal registration link, and the partner's own AI assistant all work from that same definition. Widening what a segment reaches opens it everywhere at once, and nothing a partner meets off-portal was permissioned somewhere separate.

## From website form to full portal

A new partner can go from your website to the full program without anyone on your team setting them up by hand:

1. **They apply.** A partner fills in an application form on your website. See [Set up a partner application form](/features/forms/form-builder/guides/set-up-a-partner-application-form).
2. **The partner is created.** The submission creates the partner in Introw, links the company and contact in your CRM, and sets their starting tier, phase, and experience. You can add a review step first.
3. **They are invited.** The applicant gets a portal invitation automatically.
4. **They land on a welcome experience.** A small first experience with a checklist of onboarding tasks. See [Build a progressive onboarding path](/features/partners/onboarding/guides/build-a-progressive-onboarding-path) and [Journeys](/features/partners/journeys).
5. **They sign the agreements.** Your NDA and partner agreement, in DocuSign or another signing tool, arrive as a step in onboarding. See [Get partner agreements signed](/features/partners/onboarding/guides/get-partner-agreements-signed).
6. **They move to the full experience.** Deal registration, co-selling, commissions, and MDF open up, either through a [segment](/features/partners/segments) that updates as they qualify or a [workflow](/features/automation/workflows) that switches their experience.

## Run it from your AI assistant

<Headless>
  * Show recent partner portal activity - visits, comments, and asset views - this week.
  * Which partners have been most active in the portal this month?
  * List partners in the directory by category and country.
</Headless>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.