Identity Mapping

An account has been linked to an identity through a specific attribute or relationship. This would typically be when one or more attributes (name, username, email) of an account match one or more attributes (name, username, email) of an identity. Users can perform manual account mapping to link a disparate account to an identity within Hydden.

The identity mapping page is configurable via the Columns option.

Use the Columns button to add or remove columns from your identity mapping page.

Manually Adding an Identity

1. Navigate to Configuration | Identify and select Identity Mapping.

2. Click + Add Identity.

   

3. Enter a Display Name, Email, and Alternative Emails. Several alternative emails can be added separated by a semicolon.

4. Click Add.

Identity Import

Hydden provides an option to manually import identities into an organizations tenant.

1. Navigate to Configuration | Identify.

2. On the Identity Mapping tab, select Import.

3. On the Import CSV Identities modal, click Select CSV File to open your computer’s file upload picker to upload your file.

   

4. When the file name shows in the Import CSV File field, click Import.

Status messages show if an import

• was successful or not.
• how many identities were imported or updated.
• restored an identity.

Imports are also captured in the Audit log:

Import Template

For the initial manual identities import only 4 columns are needed in the import file:

• identity.name
• identity.email
• identity.alternativeEmail
• uniqueId

Identity.name is required, meaning the csv file needs to have at a minimum identity name specified to create a record in Hydden.

Template Download

Use the Identity Import Test file as a template for your manual imports.

Create Your Own File

1. Copy the following code block.
2. Paste into a blank file and save as csv.
3. Edit the contents in any spreadsheet editing program to get started with your organizations manual identity imports.

identity.name,identity.email,identity.alternativeEmail,uniqueId
My Test Id 1,mytestid1@demo.corp,"[aaa@aaa.com,bbb@bbb.com]",b9da786a-86aa-1613-82a5-a0720d7ac666
My Test Id 2,mytestid2@demo.corp,,862360e1-bfb7-453b-8c47-65196f1670db
My Test Id 3,mytestid3@demo.corp,,
My Test Id 1-new,mytestid1-new@demo.corp,,
,mytestid2-new@demo.corp,mytestid1-new@demo.corp,
My Test Id 4,,,22334455-66554433
,mytestid5-new@demo.corp,,
My Test Id 6,mytestid6-new@demo.corp,,123456

Based on the code block data, on import you will observe that no entry is created for mytestid5-new@demo.corp and mytestid2-new@demo.corp. Those data sets do not have an identity.name specified and are ignored on import.