Profile groups are workspace-scoped. They segment profiles inside the
selected workspace. Use workspaces for logical operating
contexts such as Live and Calibration; use profile groups for dynamic
populations inside those contexts. See Profile
Groups for how segmentation works.
Key concepts
Manage profile groups
The Profile segmentation page shows the profile groups for the selected workspace. Use the Active, Archived, and All tabs to keep the active working set short while preserving older groups for audit and migration review. Each group has:- Name: the label users see in profile views, tables, and configuration history
- Description: short operational context for the segment
- Rule Priority: the tie-breaker when a profile belongs to more than one group
- Status: Active or Archived
Create a profile group
Click Create profile group, then enter the label, description, and priority. Minerva generates the internal identifier automatically. Before the group is saved, Minerva opens the standard change review dialog. Add a concise change description that explains why the segment was created or updated.Archive a profile group
Archive a group when it should no longer be used for new assignments. Archived groups remain visible in history and can still provide context for older records or migration reviews. Archive a retired group instead of renaming it to a new meaning. Reusing an old group for a different population makes past assignments and history harder to audit.Assign groups to profiles
Open a profile and use the profile edit drawer to add or remove group assignments. A profile can belong to multiple groups at the same time. Use multiple groups only when the combination is meaningful. If groups overlap, set priorities so the highest-risk or most specific segment wins for monitoring frequency overrides.Programmatic use
Profile groups can also be managed through application API key flows. This is useful when a CRM, core banking platform, case management system, or customer master is the source of truth for segmentation. The Profile Groups API covers the endpoints and payloads. Typical integration sequence:- List profile groups for the workspace and store the returned system-generated IDs.
- Create, update, restore, or archive groups when your operating model changes.
- Create or update profiles with the relevant profile group IDs.
- Remove a group ID from profiles when the profile no longer belongs to that segment.
Example use cases
Risk segmentation example
A common model is three profile groups inside the same workspace, paired with different screening frequencies. Higher-risk populations receive the highest allowed cadence, while lower-risk populations can use less frequent monitoring when policy allows. Example when organization caps are Sanctions Daily, PEP Monthly, and News Monthly:
Priority decides which group wins when a profile belongs to several. A profile assigned to both High risk and Low risk uses the High risk monitoring cadence.
These are example cadences, not a policy recommendation. Your organization can
only choose frequencies that are at or below the configured organization cap
for each feed.
Recommended operating model
- Define groups around durable operating criteria, not temporary investigations.
- Keep the number of active groups small enough for analysts and admins to understand.
- Use descriptions to explain inclusion criteria in plain language.
- Use higher priority for groups that should win when multiple groups apply.
- Pair profile group design with Screening frequencies if monitoring cadence should differ by segment.
- Review configuration history after saves and roll back when a deployment needs to be reverted.