Help Center/Governance, RBAC & Security Desk/How to create a new member with roles (Create User)
Governance, RBAC & Security Desk•Last updated: 2026-10-20•3 min read

How to create a new member with roles (Create User)

Super admins can provision an account directly: name, email, password, entity type, tenant and one or more roles from the 6-tier taxonomy.

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

Ask AI Copilot

Step-by-Step Procedure

1

Open the dialog

On /admin/users click "Create User" in the header. The dialog is titled "Create New User".

2

Fill the identity fields

Enter "Display Name *" (2-120 characters), "Email (login identifier) *" and "Password * (min 8 chars)". The password field is plain text so you can read it back to the member over a secure channel.

3

Choose entity type and tenant

"Entity Type" offers human, organization, ai agent, infrastructure and virtual entity; "Tenant" defaults to tenant:i8:community. Some entity types are not admitted by some roles and the API will refuse the combination.

4

Select roles

Under "Role Selection (6-Tier Taxonomy)" click one or more role cards grouped by "Tier N" headings. Each card shows the role name, its id and an L-clearance badge; hover to read its description. At least one role is required.

5

Review the capability preview

"Effective Capability Mesh" lists the union of permissions your chosen roles resolve to and the "Resulting clearance: L#" (the highest clearance among the roles). A "*" permission is highlighted in red because it means unrestricted access.

6

Submit

Click "Create User". On success a green "Member created" box shows the DID, roles with clearance and state; the form resets and the table refreshes. Click "Close" when done.

Expected Operational Outcome

The member exists and, per the API message, "The account is active." They can sign in with the email and password you set.

Troubleshooting & Failure Modes

Symptom: "EMAIL_EXISTS" / "An account with this email already exists"
Likely Cause: The email is already registered.
Resolution: Use a different email or open the existing member instead.
Symptom: "Select at least one role from the capability mesh."
Likely Cause: No role card was selected.
Resolution: Click at least one role card.
Symptom: "Super Administrator Level 5 clearance is required to access member provisioning"
Likely Cause: Your account is not a super admin.
Resolution: Ask a super admin to create the account.
Symptom: Warning line "Persistence warning: ..."
Likely Cause: The identity row could not be written durably (memory_only).
Resolution: Report it to the platform team; the account may disappear after a restart.

Was this guide helpful?

Help us refine our platform documentation