Segments let you group partners and partner contacts so you can target, organise, and control access to them across the whole platform. You can build segments based on partners (companies) or on partner contacts (individual people) for example a Gold partners segment of your top-tier partner companies, or a Partner Sales reps segment of every contact whose role is sales rep.
You can find all segments under Settings > Segments. From here you can see each segment's name, type, the number of members it currently contains, and whether it overrides your organisation defaults — and create a new segment. The first row, All partners · Default, is pinned: it holds the baseline permissions and notifications that apply to everyone.
Each segment opens on four tabs — General, Audience, Permissions, and Notifications — covered in order below.
General
Every segment starts with a Name and an optional Description. The name is how the segment appears everywhere it's used across the platform, so pick something clear and recognisable (e.g. Gold partners or Partner Sales reps). Use the description to explain what the segment is for and who belongs in it, which is helpful when your team grows.
Audience
The Audience defines who belongs to the segment. Segments can be dynamic or static:
Dynamic enrollment — members are determined automatically based on conditions you set. As partners or contacts change, they're added to or removed from the segment automatically, so the segment always stays up to date.
Static list — you hand-pick the exact partners or contacts that belong to the segment. Membership only changes when you edit the list yourself.
For dynamic segments, Introw offers extensive condition filtering based on both your CRM data and Introw data. You can combine conditions to target precisely the audience you want — for example all Introw certified partners, or all partner contacts where employment role = Sales rep.
How permissions and notifications are decided
The next two tabs work differently from General and Audience. Partner permissions and email notifications start from one organisation-wide default, and a segment changes that default only when you deliberately turn on an override. Every setting resolves in three steps:
All partners · Default — applies to everyone, always. It's the pinned first row in the Segments table, and its General tab shows how many segments override each setting.
Segment overrides — apply only to segments where you switched the override on, and to their members.
Contact opt-outs — let individual contacts silence notifications, nothing else.
Three rules are worth knowing before you configure anything:
Segments can restrict, not just grant. An override can turn capabilities off for its members as well as on, so you can hold a group back from something the default leaves open.
Within segments, the most permissive setting wins. If a contact matches two override segments with conflicting rules, the more permissive one applies — a segment can't hold a group back from what another segment grants.
Contacts can only opt out. When policy leaves an event on, a contact can disable their own copy. When policy turns it off, the toggle is locked and they can't switch it back on.
One restriction to keep in mind: a dynamic segment with zero conditions can't have overrides enabled — it would target everyone, which is what the default is for. Introw blocks it with: "An override segment must target a subset. Add at least one condition." Static lists are exempt.
Permissions
Permissions control what partners and contacts are allowed to do in their partner portal. Set the baseline on All partners · Default, then open a segment's Permissions tab and switch on Override the default for this segment to change it for that group. Leave the switch off and you see the org defaults read-only. Any setting that diverges from the default gets an Override badge.
Invite colleagues
Whether contacts can add coworkers to the portal. The preview shows the partner-side Your team panel. Restrict this if you only want certain partners to grow their portal access.
See all shared records
Whether contacts see all records shared with their company, or only the ones they're assigned to. The preview shows how notifications follow access — partners never get notified about records they can't reach.
Notifications
Notifications work the same way: a baseline on All partners · Default, changed per segment via Override the default for this segment. Each event has a single Recipients value:
All partners — sends to every applicable partner.
Collaborating only — sends only to assigned collaborators, for CRM-record events.
Disabled — switches the event off.
💡 Introw Tip: Slack and Teams notifications are configured on the integration itself, under Settings > Integrations > Communication tool> Partner channels, not per segment.
Checking what applies to a single contact
Open a partner contact and go to their Notifications tab. A card walks through all three layers, and each event row is badged with the layer that decided it — for example "All partners · default settings" or "Disabled · segment Tier 1". Locked rows mean policy owns the setting and the contact can't change it. The contact's Permissions tab shows a resolved yes/no per permission and names the segment or default that granted it.
Because segments are used across the whole platform, configuring audience, permissions, and notifications once lets you consistently target and govern the same group of partners or contacts everywhere in Introw.