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.
The problem it solves
A standalone portal is one more place people have to remember to visit:Impact
Adoption is decided by where something lives, not by how good it is. Putting the portal inside the product or the CRM a partner already opens is the cheapest adoption you will ever buy.See it work
How it works
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. 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.Going deeper
How to
Setup, configuration, and all how-to guides.
API reference
The embed session endpoint and code.
API Keys & REST API
Pairs embeds with API data.
CRM
Embed Introw inside the CRM.
Experiences
Embed a portal experience anywhere.