User Segments
Group your end users into reusable audiences — Enterprise, At-Risk Renewals, Acme Team — then use those segments to gate board visibility and filter your user list.
What Is a User Segment?
A user segment is a saved group of end users defined by a set of rules. Instead of repeatedly filtering by "users where MRR > 5000 AND status is Active," you define that group once as Enterprise Customers and reuse it everywhere.
Segments are organization-scoped and dynamic — when new end users match the rules, they're automatically included.
User segments are a paid feature — the Segments section is locked until your plan includes the user_segments entitlement.
Where Segments Are Used
| Use Case | How It Works |
|---|---|
| Board visibility gating | Make a board visible only to a specific segment ("Segmented Users" visibility) |
| Post-creation access | Only let users in a segment submit to a board |
| Users page filtering | Click a segment in the left rail to see only matching users |
| Inbox filtering | Filter feedback by submitter segment, including in saved views |
This is what makes segments the connective tissue between your customer data and your portal experience.
Create a Segment
Segments live on the Users page, not in Settings.
Open Segments
Go to Users in the dashboard sidebar. In the left rail, find the Segments section and click New segment.
Name your segment
Enter a Segment name (e.g., "Enterprise Customers").
Choose match type
Decide how rules combine:
- All — user must match every rule
- Any — user matches if at least one rule fits
Add rules
Each rule has three parts:
- Attribute — the user property to check
- Operator — how to compare
- Value — what to compare against (some operators, like "is null", don't need one)
Add as many rules as you need.
Save
Your segment is live immediately and appears in the Segments rail with its member count. Membership is evaluated dynamically — new end users matching the rules are automatically included.
Available Attributes
Segments can be defined on these end-user attributes:
| Attribute | Type |
|---|---|
| Name | Text |
| Text | |
| Company | Text |
| MRR | Number |
| Status | Text |
| Risk | Text |
| Renewal Date | Date |
| Joined | Date |
Company data (MRR, status, risk, renewal date) is populated via identity verification or SSO JWT claims.
Operators
The operator options depend on the attribute type:
| Type | Operators |
|---|---|
| Text | is, is not, is null, is not null, contains, does not contain, starts with |
| Number | is, is not, greater than, less than, between, is null, is not null |
| Date | after date, before date, on date, less than x days ago, more than x days ago, exactly x days ago, is null, is not null |
Examples
Using Segments to Gate Boards
The most common use of segments is restricting which end users see specific content:
- Create a Beta Customers segment
- Create a Beta Board with Who can see posts set to Segmented Users → Beta Customers
- Only end users matching the segment see the board on the portal
This is how teams run private beta programs, enterprise-only feedback channels, or staged feature rollouts — without any custom code.
See Visibility & SEO for the full visibility model.
Viewing Segment Members
Each segment row in the left rail shows its current member count. Click a segment to filter the user list to its members — there's no separate segment detail page.
Segments work best when they're stable definitions of customer groups, not one-off filters. Use saved views for ad-hoc filtering of your inbox. Use segments when you want to reuse the same group definition across multiple features.