Experiences are the no-code builder behind your partner portal: design once from stages and sections, then publish the same polished experience to every partner.
The problem it solves
A partner portal that needs engineering to change is a portal that never changes:Impact
Partner portals decay because changing them is expensive. Owning the builder is why yours still reflects this quarter’s program rather than the one you launched with.See it work
How it works
An experience is a portal layout you build from stages (the tabs partners navigate) and sections (the content blocks inside them). You assemble it visually, dropping in rich text, documents, CRM views, forms, and more, without writing code or filing an engineering ticket. Assign an experience to your partners and each gets their own partner portal based on it, so you design the portal once and deliver it consistently to everyone. You are not limited to one experience. Most programs run one per motion, because what a reseller needs on day one has almost nothing in common with what a referral or an implementation partner needs. Which experience a partner gets is set on their partner record, and a workflow can move them onto a different one when their program field changes in the CRM. Inside an experience, segments narrow it further: stages and sections can be restricted to a segment, and because a segment can filter on the contact as well as the partner, the technical contact and the commercial lead at the same reseller open the same portal and see different things. When you improve an experience, you publish the change out to the partner portals linked to it, and you can preview exactly what partners will see before you do. Reusable synced sections let you maintain shared content in one place and drop it into many experiences. The result is a partner portal your team owns and evolves on its own. Experiences put the portal in your team’s hands. You build stages and sections visually, preview the result, and publish to every linked partner portal from one place. The portal becomes something partner marketing ships and iterates on, not a project that waits on engineering.Going deeper
How to
Setup, configuration, and all how-to guides.
API reference
Integration surface and code.
Segments
Gate tabs and sections to segments.
Asset Library
Add library assets to a stage.
Form Builder
Embed forms in a stage.
Workflows
Publish a different experience to a partner automatically.