- The segmentation can change over time
- A profile can belong to more than one segment
- The segment should be visible to analysts and admins
- Ongoing monitoring cadence may differ by segment
Profile groups compared with workspaces
Each profile group has a system-generated internal ID. Admins manage the customer-facing name, description, priority, and archived status. API integrations should use the generated ID, not the label; see the Profile Groups API.
Priority decides what happens when a profile belongs to multiple groups: the higher priority group wins for profile group-specific monitoring frequency overrides. If no group override applies, the profile uses the workspace default. For setup instructions and examples, see the Profile Groups Guide and Screening Frequencies Guide.