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

# Embed

> Bring the partner experience to where partners already are - embed the portal inside your own product with an iframe, or meet partners on the record in HubSpot and Salesforce.

> Partners adopt what is in front of them. Embed lets you put Introw where partners already work: inside your own product through an iframe, or directly on the record in HubSpot and Salesforce, so partnerships happen without a separate destination.

## What it does

Embed comes in two forms. Portal embed lets you load the partner portal inside your own product through
an iframe: you authorize the domains allowed to embed it, create a key for portal sessions, and generate
an authenticated session so a logged-in user lands straight in the portal. CRM embed brings Introw onto
the record in HubSpot and Salesforce, so your team and partners see partner context where they already
sell.

Both keep partners in a familiar surface instead of asking them to learn a new tool, which is what
actually drives adoption.

## The problem it solves

A standalone portal is one more place people have to remember to visit:

* **Partners will not adopt a separate tool** → Embed the portal inside the product they already use.
* **Reps want partner context on the record** → CRM embeds put Introw on HubSpot and Salesforce records.
* **A bare iframe is not secure** → Embedding is gated by an allow-list and authenticated sessions.
* **Building an integrated experience takes months** → A guided setup and a session endpoint do the work.

## From problem to solution

Authorize your domains, create a portal-session key, and embed the portal in your product, or connect
your CRM to surface Introw on the record. Partners stay where they already work, and adoption follows.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  authorize["Authorize domain and key"] --> embed["Embed the portal or CRM"]
  embed --> access["Partner works where they are"]
```

## Use cases

<CardGroup cols={2}>
  <Card title="Embed in your product" icon="circle-check">
    Load the portal inside your app.
  </Card>

  <Card title="Embed in the CRM" icon="circle-check">
    Show partner context on the record.
  </Card>

  <Card title="Authenticate seamlessly" icon="circle-check">
    Drop users straight into the portal.
  </Card>

  <Card title="Control where it loads" icon="circle-check">
    Allow only your own domains.
  </Card>
</CardGroup>

## Impact

* **Work where you already are** - Partners use Introw inside the product or CRM they already know.
* **Composability** - Embed is a building block you place into your own surfaces.
* **Time to value** - Drop in a portal with an iframe in minutes, with minimal glue code and no custom build.

## Who it's for

<CardGroup cols={2}>
  <Card title="Developer / Integrator" icon="user">
    Embeds the portal in your product.
  </Card>

  <Card title="CRM Administrator" icon="user">
    Sets up CRM embeds on the record.
  </Card>
</CardGroup>

## Works with

{/* CONNECTS:START - generated content goes here */}

<CardGroup cols={2}>
  <Card title="API Keys & REST API" icon="code" href="/features/developer/api">
    Pairs embeds with API data.
  </Card>

  <Card title="CRM" icon="plug" href="/features/integrations/crm">
    Embed Introw inside the CRM.
  </Card>

  <Card title="Experiences" icon="browser" href="/features/portal/experiences">
    Embed a portal experience anywhere.
  </Card>
</CardGroup>

## Going deeper

<CardGroup cols={2}>
  <Card title="How to" icon="screwdriver-wrench" href="./technical">
    Setup, configuration, and all how-to guides.
  </Card>

  <Card title="API reference" icon="code" href="/general/embed-overview">
    The embed session endpoint and code.
  </Card>
</CardGroup>