Create a dynamic segment

Confirm access

Know the audience

Start a new segment

Go to Segments and create a new segment. The segment editor opens on the General tab.

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.

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.)

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).

Combine conditions to target by fit and behavior together, not just one label. Use Show audience to open the live preview panel as you build.

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.

Set permissions

On the Permissions tab, decide how this segment’s partners may act:

• Invite team members - lets partners in this segment invite their own colleagues into the portal. On by default; leave it on for trusted groups and turn it off for audiences you want to keep tightly controlled.
• Collaboration restricted - when on, deal and lead nudges show only where a partner contact is actively collaborating, rather than across all their records. Off by default; turn it on for segments where you want to limit collaboration surface area.

For contacts who belong to several segments, the most permissive setting wins: a restriction here only applies to contacts whose every segment restricts them. See Layer segments to progressively unlock capabilities.

Tune notifications

On the Notifications tab, override the default notification behavior for this audience. For each update type (announcements, comments, new records, task nudges, object updates, sleeping-deal nudges, submission outcomes, course and certificate events), you can set:

• Channel - whether the notification goes out by email, by chat, or both.
• Scope - who in the segment receives it: all partners, or only collaborating contacts.

Only override the types where this segment should differ from your program defaults; leave the rest untouched to inherit the standard behavior. For contacts in several segments, the most allowing override wins: a notification turned on in any of their segments reaches them, even if another of their segments turns it off.

Save the segment