Native claims
Native claims represent how customer data is expressed within Strivacity. This is a layer of abstraction that allows account attributes to be associated with dialects or mappings inside policies.
Viewing default and existing claims
To view the default and existing claims within Strivacity, follow these steps:
-
Start by logging into the Admin Console using an admin account.
-
From the left-hand menu, select Identities and Native claims.
Creating a new native claim
-
To create a new native claim, select Create.
-
The Create native claim screen will be displayed.
-
The table below provides an overview of the settings when creating a new native claim. Once you have completed all settings, select Save.
| Setting Name | Description |
|---|---|
| Dialect URI | A URI that uniquely identifies the claim as a native claim. This is an identifier only; it does not represent a reachable URI exposed by Strivacity. |
| Claim name | The name of the claim as it is known internally within Strivacity. Must be unique. |
| Display name | The label shown in the Admin Console. This is the name brand administrators see when editing customer information. |
| Claim description | An explanation of the claim’s purpose, shown internally in Strivacity. |
- The new native claim can now be added to an existing dialect.
Native claims can be mapped to external claim names through a dialect, so that attributes in Strivacity line up with the claim formats expected by protocols or external systems. See Dialects for details.
Default native claims
Each Strivacity instance includes a set of built-in, read-only native claims that represent commonly used identity attributes. These claims are available by default and cannot be deleted.
Default native claims are:
- City
- Company
- Country
- Department
- Family name
- Gender
- Gender (custom)
- Given name
- Job title
- Middle name
- Nickname
- Phone number
- Picture
- Postal code
- Region
- Street address
- User ID
- Username
These claims are mapped to attributes within the identity store and can be referenced in dialects, journey steps, and policies wherever native claims are supported.
Identifier native claims
In addition to the default attribute-based native claims, Strivacity provides built-in native claims that directly represent identifier values configured in the identity store.
The following identifier native claims are available:
- Identifier Email
- Identifier Phone
- Identifier Username
These claims dynamically resolve to the value configured as the account’s identifier.
For example:
- If the identity store uses email as the identifier, Identifier Email returns that value.
- If username is used as the identifier, Identifier Username returns that value.
Where identifier native claims can be used
Identifier native claims can be selected anywhere native claims are supported as a source, including:
- Dialects (for ID token mapping)
- Journey steps
- Identity verification policies
However, they cannot be configured as write targets. They are not available in:
- Physical document verification steps
- Verification data collection and display steps
- Journey input step
- Persist data target selections
- Any configuration that attempts to modify identifier values
Identifier native claims are read-only and always reflect the current identifier configuration of the account.
Updated 5 days ago