> ## Documentation Index
> Fetch the complete documentation index at: https://docs.heygarth.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# User Mappings

> Review and resolve user aliases detected across your connected tools into a single canonical identity.

The **User Mappings** page helps you reconcile the different usernames, emails, and handles a single person may have across your connected tools (for example, a GitHub username vs. their work email) into one canonical user identity. This page lives under **Administration → User & Team Management** in the left sidebar.

<Frame>
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/na-f445b234/images/user-mappings.png" alt="User Identity Mapping page" />
</Frame>

## Why this page exists

When G360 pulls data from your connected tools, the same person can show up under different identities — for example, a GitHub username that doesn't obviously match their company email. This page surfaces every such **alias** it has detected and lets you confirm which canonical user it actually belongs to, so activity from all their tools rolls up under one identity instead of being split across several.

## Summary cards

At the top of the page, four cards give you a live count of aliases by status. Clicking a card also filters the table below to just that status:

| Card            | What it shows                                                                                              |
| --------------- | ---------------------------------------------------------------------------------------------------------- |
| **All Aliases** | Total number of aliases detected across all connected tools.                                               |
| **Pending**     | Aliases that haven't been reviewed yet and are still awaiting a decision.                                  |
| **Accepted**    | Aliases that have been confirmed and merged into their matched entity.                                     |
| **Standalone**  | Aliases that were deliberately kept as their own separate identity rather than merged into another entity. |

## Searching and filtering

Use the **Search by name, email, or username** box to find a specific alias. Below it, the **All / Pending / Accepted / Standalone** buttons let you filter the table to just that status — the count on the far right (e.g. "36 aliases") updates to reflect the current filter.

## Understanding the table

Each row represents one alias awaiting (or already given) a decision:

| Column           | What it shows                                                                                                                                          |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Alias**        | The raw identity as seen in the connected tool — its username/handle, associated email, and a badge showing which tool it came from (e.g. **GitHub**). |
| **Entity Match** | The canonical user G360 believes this alias belongs to. See below for details.                                                                         |
| **Status**       | **Pending**, **Accepted**, or **Standalone**.                                                                                                          |
| **Activity**     | The current review state — shows **Awaiting review** for aliases that haven't been actioned yet.                                                       |
| **Actions**      | **✓ Accept** and **⊘ Standalone** buttons — see below.                                                                                                 |

### Entity Match

Under each alias, G360 suggests the canonical user it's most likely to belong to, shown as a dropdown you can change if the suggestion is wrong. Below the dropdown, a preview card shows details about the currently selected match:

* **Name and email** of the matched canonical user.
* **Score** — a confidence score (0 to 1) indicating how strongly this alias matches that user; a higher score means a stronger match.
* **X alias(es) · X source(s)** — how many aliases and connected tools are already linked to that canonical user.

If the suggested match isn't correct, use the dropdown to select a different canonical user before deciding how to resolve the alias.

### Resolving an alias

For each pending alias, choose one of two actions:

* **✓ Accept** — confirms the alias belongs to the user shown in **Entity Match**, and merges it into that canonical identity. Their activity across tools will now roll up under that one user.
* **⊘ Standalone** — keeps this alias as its own separate identity, and does **not** merge it into any other user. Use this when the alias genuinely belongs to a different person than the one suggested, or doesn't match anyone else in the system.

<Note>
  Once an alias is marked **Accepted** or **Standalone**, it moves out of the Pending queue and its status updates in the table (and in the summary cards) accordingly.
</Note>