What you’ll achieve
A dynamic segment whose membership follows your conditions automatically, with collaboration permissions and notification behavior set for that audience. Point any feature (a portal experience, a course, a campaign) at the segment and it stays targeted at the right partners, who collaborate and get notified exactly as you intend.Before you start
1
Confirm access
You need access to segment settings. A connected CRM lets a dynamic segment filter on live partner data.
2
Know the audience
Decide what makes a partner belong (for example tier, region, or lifecycle phase) so your conditions capture fit and behavior, not just one label.
Watch it
- Video
- Click through
Steps
1
Start a new segment
Go to Segments and create a new segment. The segment editor opens on the General tab.

2
Name the segment
On the General tab, fill in the basics:
- Segment name - how the segment appears everywhere you use it (for example “Enterprise partners”). Required, and worth making self-explanatory since teammates pick it from lists.
- Description - an optional note for your team about who this segment is for. It does not affect membership.

3
Choose dynamic enrollment
On the Audience tab, set Enrollment type to Dynamic. Dynamic means membership auto-updates from conditions: partners entering or leaving the criteria are added or removed in real time as CRM properties change. (Choose Static instead only when you need a fixed, hand-picked list - see Create a static segment.)

4
Define the audience with conditions
Still on the Audience tab, build the rules that decide who belongs:
- Partner conditions - rules on partner-level fields (such as tier, phase, country, or a CRM property). Use these to target by organization-level fit.
- Contact conditions - rules on the people at those partners, when you want to narrow to contacts who match (such as a role or activity signal).

5
Check the preview
Review the audience preview of who currently matches, with its partner and contact counts, to confirm the segment captures the right people before you rely on it.

6
Set permissions
On the Permissions tab, switch on Override the default for this segment first. Until you do, the segment follows your organisation default and the panel is read-only, showing you what its members currently get.Both are phrased as grants, so more permission always reads as on.
- Invite colleagues - lets partners in this segment invite their own coworkers into the portal, and invited colleagues inherit the organisation default.
- See all shared records - when on, a contact sees everything shared with their company. Turn it off and they see only the records they are assigned as a collaborator on, with notifications following that access.
Each card says which side of your default it is on, and moving it back is how the segment goes back to following the default. Across overlapping segments both resolve the same way, most-permissive: an invite grant in any of them wins, and See all shared records switched on in any of them wins.

7
Tune notifications
On the Notifications tab, switch on Override the default for this segment, then set the recipients per event (announcements, comments, new records, task nudges, object updates, sleeping-deal nudges, submission outcomes, course and certificate events):
- All partners - everyone in the segment the event applies to.
- Collaborating only - just the contacts assigned as collaborators on the record. Offered only for events attached to a CRM record.
- Disabled - the event does not send to this segment.

8
Save the segment
Save to create the segment. Membership now updates on its own as partner data changes, and the permissions and notification settings apply to everyone the conditions capture.

Verify it worked
The segment shows its current members on Segments, and the count shifts as matching partner data changes. The segment also shows where it is used across the product, so before you later edit or delete it you can see its reach.Related
Create a static segment
Hand-pick a fixed audience instead.
Restrict a tab to segments
Use the segment to gate portal content.
Layer segments to progressively unlock capabilities
How overlapping segments resolve, and how to design around it.
Implementation reference
Full configuration options for segments.