Profile groups let your organization segment monitored profiles inside a workspace without creating a new workspace for every operational cohort. Use them for risk, product, geography, diligence, service model, or other internal criteria that can change over time. Access: Requires the Admin role or above. In the sidebar, go to Administration > Configuration, then open Profile segmentation under Screening behaviours. Use this guide when you need to:Documentation Index
Fetch the complete documentation index at: https://docs.gominerva.com/llms.txt
Use this file to discover all available pages before exploring further.
- create customer-facing segment labels for monitored profiles
- assign profiles to one or more segments
- understand how profile group priority works
- keep retired segments available for audit context
- plan profile group use cases for risk segmentation
Profile groups are workspace-scoped. They help 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.
Key Concepts
| Concept | What it means |
|---|---|
| Profile group | A workspace-scoped segment that can be assigned to profiles. Examples include Enhanced diligence, Cross-border commercial, or Retail standard monitoring. |
| Profile assignment | A profile can belong to more than one group. This is useful when several criteria apply to the same customer. |
| Priority | Higher priority wins when a profile belongs to multiple groups and more than one group has monitoring frequency overrides. |
| Archived group | A retired segment retained for history and migration context. Archived groups should not be used for new assignments. |
| Internal identifier | The system-generated ID used by APIs and integrations. Admins manage labels, descriptions, and priority in the UI. |
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 instead of renaming a retired group into 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. 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
| Use case | Example group | Why it helps |
|---|---|---|
| Enhanced due diligence | Enhanced diligence | Applies a clear label to customers that require higher-touch review. |
| Product exposure | Cross-border commercial | Separates customers with products that create different monitoring needs. |
| Lower-risk retail | Retail standard monitoring | Keeps standard populations distinct from elevated-risk groups. |
| Private banking | Private wealth | Supports service-model segmentation without creating a separate workspace. |
| Migration cleanup | Retired pilot segment | Preserves context for historical assignments while stopping new usage. |
Example: High, Medium, And Low Risk Segments
A common risk-segmentation model is to create three profile groups inside the same workspace and pair them 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:| Profile group | Priority | Example population | Sanctions cadence | PEP cadence | News cadence |
|---|---|---|---|---|---|
| High risk | 90 | Enhanced diligence, high-risk geography, elevated product exposure | Daily | Monthly | Monthly |
| Medium risk | 50 | Standard commercial or retail populations with some risk indicators | Weekly | Monthly | Monthly |
| Low risk | 10 | Lower-risk, domestically focused, stable retail or dormant populations | Monthly | Quarterly | Quarterly |
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 use rollback when a deployment needs to be reverted.