Users & Wallet Users
Two tabs covering two different kinds of user: Ledger users with their rights, and users onboarded to the Wallet UI.
Overview
Users
Ledger users on the Canton participant. A ledger user has rights over specific parties, and is what an application authenticates as when it talks to the Ledger API.
Wallet Users
Wallet UI users registered with the validator app, so a person can sign in to the Canton Wallet.
Neither creates an account in your identity provider. Both assume the identity already exists there.
Users
The heading shows the count: n users provisioned on this validator.
Columns
Username
The ledger user ID
Primary party
The party the user acts as by default
Identity provider
The identity provider ID, or default
Active
Active or Deactivated
—
Edit action
Viewing rights
Clicking a row opens a read-only drawer showing the user's rights, grouped by kind:
Participant admin
Full administrative control of the participant.
Identity provider admin
Administration of identity provider configuration.
Can read as any party
Read access to every party's data on this participant.
Can execute as any party
Execution on behalf of any party.
Can act as
Submitting commands on behalf of the listed parties.
Can read as
Reading the listed parties' data.
Can execute as
Executing on behalf of the listed parties.
The drawer's Edit Rights button moves you into the editor.
The first four are participant-wide rights, not party-scoped. Participant admin and Can read as any party in particular give access to every party's data on the node. Grant them sparingly, and prefer the party-scoped rights below them.
Creating a user
Click Create User
Provision a new participant user with a primary party and rights.
Fill in Basic info
User ID is required — for example analyst-01. Primary party is optional.
Grant rights
Under Rights, add parties to Can act as, Can read as, and Can execute as. Type a party and press Enter — each becomes a removable chip. Under Global flags, tick any participant-wide rights.
Click Create
The modal closes on success.
Editing a user
The pencil icon on a row, or Edit Rights in the drawer, opens the same modal in edit mode: User ID is read-only. Primary party, status, annotations and rights can be changed.
Edit mode adds:
a Deactivated checkbox — user cannot authenticate to the ledger;
an Annotations section for arbitrary key/value metadata on the user.
Saving rights replaces them wholesale. The editor is not additive — the rights shown when you save become the user's complete set, and anything you removed is revoked. Always open the editor from the row or drawer so it is pre-populated with the current rights, rather than reconstructing them from memory.
States
No users
No users yet — Create the first user to grant ledger access.
Load failed
Failed to load users, with the error
Wallet Users
The heading shows the count: n users registered with the wallet UI.
Username
The wallet username, with a copy button
Status
Always Active
—
Remove action
Adding a wallet user
Add Wallet User — Enter a username to onboard someone to the wallet UI. Enter the Username and click Add user. A toast confirms Wallet user added.
The UI checks for duplicates before submitting and warns Username already exists rather than sending the request.
The username must match the user's identity in your identity provider. Onboarding a username that does not exist there creates a wallet user nobody can sign in as.
Removing a wallet user
The trash icon opens a confirmation: Offboard "<username>" from the wallet UI. This cannot be undone. Confirm with Remove.
This is the only destructive action in the UI that asks for confirmation, and it cannot be undone. The validator refuses to offboard its own wallet user, so that request will fail with a conflict rather than breaking the validator.
States
No wallet users
No wallet users yet — Add a username to give someone access to the wallet UI.
Load failed
Failed to load wallet users, with the error
Last updated
Was this helpful?