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

# Aliases

Aliases are unique, non-verifiable authentication identifiers (authN IDs) that an end user can register to their Digital Identity Management profile.

An user can sign in to Digital Identity Management using their alias and password instead of their email address or mobile number. Examples of an alias might include a personal nickname, an account number, or any other username defined by the user. Aliases must be unique across your organization's Digital Identity Management data store. If one user registers the alias **BicycleFan**, then no other user can register the same alias.

Aliases are not linked to a verifiable contact channel like an email address or mobile number. Therefore, an alias cannot be verified in the same way as an email address or mobile number. Once a user registers an alias or if you register it on behalf of them, then it is **Activated** and usable immediately.

You can perform the following tasks upon user request:

* [Add an Alias](addingAlias)
* [Update an Alias](updatingAlias)
* [Remove an Alias](removingAlias)

**Note:** The Process APIs support aliases by default. However, your organization can opt to not allow your end users to register aliases. Your organization's developers may not include the options for end users when building user-facing applications. In this case, you may want to skip the alias options in Digital Identity Management Care.

* **[Add an Alias](../topics/addingAlias)**

* **[Update an Alias](../topics/updatingAlias)**

* **[Remove an Alias](../topics/removingAlias)**

**Parent topic:**[Update a User's Details](../topics/sgUpdatingProfile)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.