Skip to main content
Open in Introw: Experiences

​
How it works

Progressive onboarding is not a single setting; it is a pattern you assemble from pieces that already exist. Three of them do the work together:
  • Journeys give a partner the ordered checklist that drives them forward, from first login to first deal. See Journeys.
  • Dynamic segments decide which stage a partner has reached. A dynamic segment’s membership updates automatically from its filters, so as a partner completes a journey, earns a certificate, reaches a tier, or a CRM property flips, they move into the next segment without anyone touching it. See Segments.
  • Portal experiences restrict tabs and sections to segments. A tab or section gated to a segment is only visible to partners in it, so the portal reveals more as a partner qualifies. See Experiences.
Put together: define a segment per onboarding stage, gate the matching tabs, asset sections, and ability-bearing blocks (forms, deal registration, courses) to those segments, and let journeys push partners forward. A partner sees only their current stage, and the next one appears the moment they qualify.

​
Prerequisites

  • A published portal experience partners can reach. See Experiences.
  • Permission to create segments and edit experiences.
  • A connected CRM so dynamic segments can filter on live partner data.
  • The milestones you want to gate on, such as a journey, certificate, or tier, set up.

​
Settings & configuration

You assemble onboarding across Segments and the Experience builder.

​
Define a segment per stage

Create a dynamic segment for each onboarding stage and set its audience filters to the condition that defines that stage, for example onboarding journey complete, a certification earned, or a tier reached. Membership recomputes as partner data changes, so partners enter the segment automatically when they qualify. Use the audience preview to sanity-check who currently matches. Stage filters do not need to exclude earlier stages. A partner in a later stage usually still matches the earlier segments, and that overlap is safe: when a contact belongs to several segments, the most permissive settings win, so each stage a partner earns only ever adds capabilities. See Layer segments to progressively unlock capabilities.

​
Gate tabs and sections

In the experience, restrict a tab to specific segments so only partners in a stage see it, and do the same for sections within a stage. Gate the asset sections, forms, and other ability-bearing blocks that should unlock at each stage. Partners not yet in the segment simply do not see the gated content.

​
Drive partners forward

Apply an onboarding journey so partners have a concrete checklist. As they complete it (and the other milestones your segments key on), they roll into the next stage’s segment and the matching tabs unlock.

​
Tune what each stage can do

Segment permissions control abilities like inviting teammates or collaboration scope, so a stage can unlock not just content but what a partner is allowed to do. Configure each stage with only what it grants, and keep your most restricted settings on a default segment that captures everyone: permissions and notifications resolve to the most permissive across a contact’s segments, so a restriction only applies when every segment a contact belongs to imposes it. See Create a dynamic segment.

​
Setup walkthrough

1

Map the stages

Decide the onboarding stages and the milestone that promotes a partner from each one to the next.
2

Create a segment per stage

On Segments, build a dynamic segment for each stage from its qualifying filters.
3

Gate the experience

In Experiences, restrict each tab and section to the segment that should unlock it.
4

Apply a journey

Give partners an onboarding journey so they have a clear path forward.
5

Preview and publish

Preview as partners in different stages, then publish the experience.

​
How-to guides

Build a progressive onboarding path

Plan onboarding stages, create a dynamic segment per stage, gate portal tabs, sections, and abilities to those segments, and let journeys move partners forward so the portal unlocks as partners qualify.

​
Limits & gotchas

Unlocking is only as accurate as the segment filters, so a partner who does not match a stage’s filters will not see its tabs, test the qualifying conditions before launch. Dynamic segment membership cannot be edited partner by partner; change the filters to change who qualifies. Publishing pushes experience changes to linked rooms, so preview each stage first. A partner with no experience assigned cannot be invited at all.

​
Troubleshooting

  • A qualified partner is not seeing a new tab - confirm they match the stage segment’s filters and the tab is restricted to that segment.
  • Everyone sees everything - the tabs are not restricted to segments, or the segments are too broad.
  • A partner never advances - the milestone the segment keys on is not being met or recorded; check the journey, certificate, or CRM property.
  • A stage’s content changed for the wrong partners - a gated section used a segment broader than intended.
  • A stage’s restriction is not applying - the contact belongs to another segment that grants more, and the most permissive setting wins; put restrictions on the default segment everyone shares, not on a stage.