Embed

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.

​

Use cases

​

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

​

Works with

​

Going deeper