---
title: "User account mapping"
slug: "identity-mapping"
status: "update"
updated: 2026-09-22T08:05:25Z
published: 2026-09-22T08:05:25Z
canonical: "docs.britive.com/identity-mapping"
---

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

# Identity mapping

User account, service identity, or AI identity mapping is required for some applications where a Britive identity needs to be mapped to a target application identity to check out a profile. Usually, after an application is onboarded and scanned, all users are mapped from the onboarded application. These mapped users are ready to check out the profiles. With dynamic identity mapping, the user no longer needs to scan the applications to map new user accounts or service identities to the profiles. When checking out a profile, the Britive user is dynamically matched with the application's user account. This applies to all applications that require user/service identity mapping.

Depending on the onboarded application, you can either map the user account, service, or AI identity:[](/v1/docs/identity-mapping#user-account-mapping)

- [User Account Mapping](/v1/docs/identity-mapping#user-account-mapping)
- [Service Identity Mapping](/v1/docs/identity-mapping#service-identity-mapping)
- [AI Identity Mapping](/v1/docs/identity-mapping#ai-identity-mapping)

## User Account Mapping

All applications except AWS and OCI applications are required to map user accounts.

To map a user account:

1. Log in to Britive with administrator privileges.
2. Click on **System admin** -> **Tenant Applications**.
3. Click on the application and select **Data** from the navigation menu.
4. Click on the **Accounts** tab, and the list displays all the users. You can filter the users by clicking the **High Risk** or **With Permissions Only** icons.
5. Click on the **Map/Unmap** button from the **Actions** column of any user to add/remove the mapping.
6. Select the identity (users) and click the **+** icon in the **Actions** column to map the identity. You can map multiple users from the same page.
7. Click **OK**.

## Service Identity Mapping

Britive service identities can be mapped with service accounts in GCP and service principals in the Azure application.

Only one service identity can be mapped to one service account/principal.

To map a service identity:

1. Log in to Britive with administrator privileges.
2. Click on **Admin** -> **Tenant Applications**.
3. Click on the application and select **Data** from the navigation menu.
4. Click on the **Accounts** tab, and the list displays service accounts for this application. You can filter the users by clicking the **High Risk** or **With Permissions Only** icons.
5. Click on the **Map/Unmap** button from the **Actions** column of a service account to map/unmap the service identity.
6. Select the service identity in the **Map Identity** window and click **+** from the **Actions** menu to map/unmap the identity.

## AI Identity Mapping

Britive AI identities can be mapped with service accounts in GCP and service principals in the Azure application.

Only one AI identity can be mapped to one service principal in an Azure application and one service account in GCP applications.

> [!NOTE]
> Note:
> 
> You must have the **Scan AI Identities** option enabled during the onboarding of an application. For more information, see
> 
> - [Onboarding Azure Application](/v1/docs/onboarding-azure-steps)
> - [Onboarding GCP Application](/v1/docs/onboarding)
> - [Onboarding GCP Standalone Application](/v1/docs/onboarding-gcp-standalone-application)
> - [Onboarding GCP-WIF Application](/v1/docs/onboarding-gcp-wif-app)

To map an AI identity:

1. Log in to Britive with administrator privileges.
2. Click on **Admin** -> **Tenant Applications**.
3. Click on the application and select **Data** from the navigation menu.
  1. For Azure applications, select an Azure subscription from the drop-down list.
  2. For GCP applications, select the service account from the drop-down list.
4. Under the **AI Identities** tab, a list of scanned AI identities is displayed.
5. Click on the **Map/Unmap** button from the **Actions** column to map/unmap the AI identity.
6. Select the AI identity in the **Map Identity** window and click **+** from the **Actions** menu to map/unmap the identity.