> ## 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.

# Profile Groups Guide

> How to create and use profile groups for dynamic customer segmentation in Screening.

export const StorybookFrame = ({storyId, title, version = "20260419-1", height, zoom = 0.7, preferLocalPreview = false}) => {
  const HOSTED_STORYBOOK_BASE_URL = "https://minerva-storybook.s3.ca-central-1.amazonaws.com/iframe.html";
  const isLocalDocsPreview = typeof window !== "undefined" && ["localhost", "127.0.0.1"].includes(window.location.hostname);
  const storybookBaseUrl = preferLocalPreview && isLocalDocsPreview ? "http://localhost:6006/iframe.html" : HOSTED_STORYBOOK_BASE_URL;
  const params = new URLSearchParams({
    id: storyId,
    viewMode: "story",
    singleStory: "true",
    shortcuts: "false",
    toolbar: "0",
    nav: "0",
    panel: "0"
  });
  params.set("v", version);
  const src = `${storybookBaseUrl}?${params.toString()}`;
  const unscaledHeight = `${Math.ceil(height / zoom)}px`;
  const unscaledWidth = `${100 / zoom}%`;
  return <div style={{
    width: "100%"
  }}>
      <div style={{
    height: `${height}px`,
    overflow: "hidden",
    border: "1px solid #e2e8f0",
    borderRadius: "12px",
    backgroundColor: "#ffffff",
    display: "flex",
    justifyContent: "center",
    alignItems: "flex-start"
  }}>
        <iframe src={src} title={title} loading="lazy" style={{
    width: unscaledWidth,
    height: unscaledHeight,
    transform: `scale(${zoom})`,
    border: "0",
    display: "block",
    transformOrigin: "top center",
    flexShrink: 0
  }} allowFullScreen></iframe>
      </div>
    </div>;
};

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 <strong>Admin</strong> role or above. In the sidebar, go to <strong>Administration</strong> > <strong>Configuration</strong>, then open <strong>Profile segmentation</strong> under <strong>Screening behaviours</strong>.

Use this guide when you need to:

* 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

<Info>
  Profile groups are <strong>workspace-scoped</strong>. They help segment
  profiles inside the selected workspace. Use{" "}
  <a href="/workspaces-guide">workspaces</a>
  for logical operating contexts such as Live and Calibration; use profile
  groups for dynamic populations inside those contexts.
</Info>

## Key Concepts

| Concept                              | What it means                                                                                                                                             |
| ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <strong>Profile group</strong>       | A workspace-scoped segment that can be assigned to profiles. Examples include Enhanced diligence, Cross-border commercial, or Retail standard monitoring. |
| <strong>Profile assignment</strong>  | A profile can belong to more than one group. This is useful when several criteria apply to the same customer.                                             |
| <strong>Priority</strong>            | Higher priority wins when a profile belongs to multiple groups and more than one group has monitoring frequency overrides.                                |
| <strong>Archived group</strong>      | A retired segment retained for history and migration context. Archived groups should not be used for new assignments.                                     |
| <strong>Internal identifier</strong> | 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.

<StorybookFrame storyId="pages-tenant-config-profile-segmentation--default" title="Profile Segmentation Configuration Page" height={820} version="20260530-profile-groups" />

Each group has:

* <strong>Name</strong>: the label users see in profile views, tables, and
  configuration history
* <strong>Description</strong>: short operational context for the segment
* <strong>Rule Priority</strong>: the tie-breaker when a profile belongs to more
  than one group
* <strong>Status</strong>: Active or Archived

Use the hover help icons on table labels and form labels for field-specific guidance.

### Create A Profile Group

Click <strong>Create profile group</strong>, then enter the label, description, and priority. Minerva generates the internal identifier automatically.

<StorybookFrame storyId="pages-tenant-config-profile-segmentation--create-dialog" title="Create Profile Group Dialog" height={760} version="20260530-profile-groups" />

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.

<Tip>
  Keep group names stable and business-readable. For example, use{" "}
  <strong>Enhanced diligence</strong> instead of a project code or internal key.
</Tip>

### 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.

<StorybookFrame storyId="components-screening-edit-profile-drawer--profile-groups" title="Profile Edit Drawer With Profile Groups" height={860} version="20260530-profile-groups" />

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:

1. List profile groups for the workspace and store the returned system-generated IDs.
2. Create, update, restore, or archive groups when your operating model changes.
3. Create or update profiles with the relevant profile group IDs.
4. Remove a group ID from profiles when the profile no longer belongs to that segment.

<Warning>
  Do not depend on group labels as API identifiers. Labels can be renamed by
  admins. Use the system-generated profile group ID returned by the API.
</Warning>

## Example Use Cases

| Use case               | Example group                               | Why it helps                                                               |
| ---------------------- | ------------------------------------------- | -------------------------------------------------------------------------- |
| Enhanced due diligence | <strong>Enhanced diligence</strong>         | Applies a clear label to customers that require higher-touch review.       |
| Product exposure       | <strong>Cross-border commercial</strong>    | Separates customers with products that create different monitoring needs.  |
| Lower-risk retail      | <strong>Retail standard monitoring</strong> | Keeps standard populations distinct from elevated-risk groups.             |
| Private banking        | <strong>Private wealth</strong>             | Supports service-model segmentation without creating a separate workspace. |
| Migration cleanup      | <strong>Retired pilot segment</strong>      | 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](/screening-frequencies-guide). 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 |
| ---------------------------- | -------- | ---------------------------------------------------------------------- | ----------------- | ----------- | ------------ |
| <strong>High risk</strong>   | 90       | Enhanced diligence, high-risk geography, elevated product exposure     | Daily             | Monthly     | Monthly      |
| <strong>Medium risk</strong> | 50       | Standard commercial or retail populations with some risk indicators    | Weekly            | Monthly     | Monthly      |
| <strong>Low risk</strong>    | 10       | Lower-risk, domestically focused, stable retail or dormant populations | Monthly           | Quarterly   | Quarterly    |

Use priority to ensure the higher-risk group wins when a profile belongs to
multiple groups. For example, a profile assigned to both <strong>High
risk</strong> and <strong>Low risk</strong> should use the High risk monitoring
cadence.

<Note>
  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.
</Note>

## Recommended Operating Model

1. Define groups around durable operating criteria, not temporary investigations.
2. Keep the number of active groups small enough for analysts and admins to understand.
3. Use descriptions to explain inclusion criteria in plain language.
4. Use higher priority for groups that should win when multiple groups apply.
5. Pair profile group design with [Screening Frequencies](/screening-frequencies-guide) if monitoring cadence should differ by segment.
6. Review configuration history after saves and use rollback when a deployment needs to be reverted.

## Related Guides

* [Profile Groups Concept](/concepts/profile-groups)
* [Screening Frequencies Guide](/screening-frequencies-guide)
* [Screening Guide](/screening-guide)
* [Workspaces Guide](/workspaces-guide)