# Primary Identity

<figure><img src="/files/Qr1VrbHr78seYeX0W2KT" alt=""><figcaption></figcaption></figure>

The MNS's Primary Identity feature enables users to set one identity as their primary representation on the blockchain.&#x20;

{% hint style="info" %}

* By default, the first identity claimed is automatically set as Primary
* At any given time, only one identity can hold the **Primary** status
  {% endhint %}

## Managing Primary Identity

### **Clearing the Current Primary Identity**

{% stepper %}
{% step %}
**Access Identity Management Interface**\
The user accesses the [My Identities page](https://www.modular.name/profile) to interact with their claimed identities.
{% endstep %}

{% step %}
**Initiate Set as Primary Transaction**

After selecting the identity they wish to set as the new Primary Identity, the user activates the "Menu" or chooses the "Set as Primary" option directly on the Identity page, indicating their desire to assign this identity as Primary.
{% endstep %}

{% step %}
**Transaction Request Generation**\
This selection initiates a new transaction request to the underlying smart contracts to update the Primary identity designation.
{% endstep %}

{% step %}
**Transaction Signing**\
The user must sign this transaction in the modal wallet window, confirming their intent to assign the selected identity as Primary. This step is essential for executing the changes on the blockchain and typically includes a gas fee.
{% endstep %}

{% step %}
**Update Confirmation**\
After the transaction processes, the smart contracts verify and update the records to reflect the new Primary Identity.
{% endstep %}

{% step %}
**Blockchain Validation**\
The updated Primary Identity can now be confirmed through blockchain explorers, where it displays as the active identity for all relevant transactions.
{% endstep %}
{% endstepper %}

***

### **Setting a New Primary Identity**

{% stepper %}
{% step %}
**Access Identity Management Interface**\
The user navigates to the [My Identities page](https://www.modular.name/profile) to view their existing claimed identities.
{% endstep %}

{% step %}
**Initiate Clearing Primary Identity**&#x20;

By triggering the "Menu" button of the currently set Primary Identity or selecting the "Clear Primary" option on the Identity page, the user signals the intent to remove the Primary designation from the identity.
{% endstep %}

{% step %}
**Transaction Request Generation**\
The action generates a transaction request directed to the smart contracts responsible for managing identity attributes, requesting the revocation of the Primary status.

{% endstep %}

{% step %}
**Transaction Signing**\
The user must authenticate this request by signing the transaction in their connected wallet. This step is essential for executing the changes on the blockchain and typically includes a gas fee. The signed transaction is then sent to the blockchain for processing.
{% endstep %}

{% step %}
**Confirmation of Action**\
Upon successful execution, the smart contracts update the identity registry, confirming that there is currently no identity marked as Primary.
{% endstep %}
{% endstepper %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://snowball-mns.gitbook.io/snowball/modular-naming-service-mns/identity-management-system/primary-identity.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.