- 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
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.
Priority is used when a profile belongs to multiple groups. Higher priority groups win 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.