Help Center/Governance, RBAC & Security Desk/How to edit a member's DID, name, email and role
Governance, RBAC & Security Desk•Last updated: 2026-10-20•3 min read

How to edit a member's DID, name, email and role

In the profile drawer, "Edit DID" opens a form to change the DID and identity attributes of a member. The account status is shown but changed elsewhere.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Open the member profile

On /admin/users click "Profile" for the member. Stay on the "Overview & Identity" tab.

2

Start editing

Click "Edit DID" (tooltip "Edit User DID and Identity Attributes") or the small "Edit" next to the User DID.

3

Change the fields

Fields: "User DID *" (placeholder did:i8:human:username), "Display Name", "Primary Email" and "Primary Role" (every role in the platform role registry with its clearance level; a role not in the registry is still offered so the current value is kept). "Account Status" is shown read-only: it is changed with the Account Status button (see the suspend / deactivate guide).

4

Save

Click "Save Changes". The form checks the DID is not empty and starts with "did:i8:" before calling PATCH /api/admin/members/{userId}. On success you see "Sovereign DID & Identity updated successfully!" and the table row updates.

5

Cancel if needed

Click "Cancel" to discard the edit.

Expected Operational Outcome

The member record shows the new DID, name, email and role in the drawer and the directory table. A DID change is applied to the tables that key on it (wallets, network nodes, referrals, sessions, handles); audit ledger rows keep the DID that acted at the time.

Troubleshooting & Failure Modes

Symptom: DID must begin with "did:i8:"
Likely Cause: The DID field does not start with did:i8:.
Resolution: Prefix the DID correctly, for example did:i8:human:username.
Symptom: DID is already assigned to another identity
Likely Cause: Another member already owns that DID.
Resolution: Choose a unique DID.
Symptom: Member not found in registry
Likely Cause: The member no longer exists.
Resolution: Refresh the directory.
Symptom: Only a Super Administrator may change a member's role.
Likely Cause: You changed "Primary Role" without super admin rights.
Resolution: Leave the role as it was, or ask a Super Administrator.
Symptom: STATUS_CHANGE_NOT_HERE
Likely Cause: A request tried to change the status through the profile form.
Resolution: Use the Account Status button: it revokes sessions and records the reason.

Was this guide helpful?

Help us refine our platform documentation