Users lists the people who sign in to the organisation. From it you invite or create a user, open a user to see whether their on-chain identity is registered and their KYC profile approved, and review that profile.
A login and an identity are separate records. The login decides who can sign in to the Console or the Investor portal. The on-chain identity, a contract the organisation's identity registry records for a wallet, is what a regulated token checks before it lets the wallet hold or receive value. A user can sign in with no registered identity, but cannot hold a regulated token until the identity is registered, so the user's page in the Console shows both records. A counterparty with no login belongs in Contacts, and a token or other contract identity belongs in Entities.
The “Users” tab lists each user with name, type, identity registration, KYC status and country.
The email column is hidden by default and you turn it on from the column picker. “Search users…” matches name, email, national ID, the user's wallets and the identity address registered to one of them. The “Create or invite user” button sits in the page header.
Steps
Start the invitation or the account
Select Create or invite user. “Send invitation email” is on by default. Enter the invitees. When you may grant at least one on-chain role, the field is “Email addresses” and takes up to 100 addresses, separated by commas, spaces or new lines. Otherwise the field is “Email” and takes one address. Choose the “Organisation role”, “Member” or “Owner”, and optionally the “On-chain permissions” the invitees receive when they complete onboarding. The roles offered are the ones you may grant. Select “Send invitations”.
Clear Send invitation email to create the account now instead. Enter the “Email” and an optional “Name” of up to 255 characters, then select “Create user”. Direct creation makes the login, a person participant, a wallet on the organisation's managed custody provider and an on-chain identity in one step. It does not register the identity and grants no on-chain role. The checkbox shows only when you may both invite and create. When you may do only one of the two, the sheet offers only that one.
The “Create or invite user” sheet with “Send invitation email” ticked.
The sheet is described as “Send an invitation by default, or create the wallet and identity now without emailing the recipient.” It shows an “Email addresses” field, an “Organisation role” picker set to “Member”, and an “On-chain permissions” list of protocol-level roles, each with its description. With “Send invitation email” cleared, the sheet shows “Email” and “Name” instead.
Confirm with your wallet verification
The Console asks you to Verify your identity with your transaction PIN or transaction code before it sends invitations or creates the user. Direct creation waits for the managed custody provider. “Checking custody provider…” shows while the Console reads it, and the sheet refuses to create with “No custody provider serves this network, so no user can be created.” when none serves the active network.
Manage invitations
The Invitations tab lists the invitations sent from this organisation. The table shows “Email”, “Expires at”, “Status” and “Actions”. “Expires at” has a date only for a pending invitation. An invitation that was accepted, rejected or cancelled cannot expire, so its cell stays empty. The statuses are “Pending”, “Accepted”, “Rejected”, “Canceled”, “Expired” and “Accepted, roles not granted”. The row menu offers “Copy invitation link”, “Resend invitation” and “Cancel invitation”. With no invitation the tab shows “No invitations yet”.
- Copy invitation link copies the link to share with the invitee. When email is not configured, the Console shows the link to share when it creates the invitation.
- Resend invitation asks you to confirm, then sends the invitation again. An invitation that expired while pending keeps its row actions.
- Cancel invitation cannot be undone. It asks you to confirm, or select “Keep invitation” to stop. The invitation stays in the list as “Canceled” for the audit trail, and the invitee's link stops offering sign-up. To give access again, send a new invitation.
Open a user
Select a user to open their page. The header shows the name, the type (or Owner for an organisation owner who holds an admin role) and the global eligibility verdict: “Eligible under global rules”, “Needs action under global rules” or “Blocked by global rules”. That verdict covers the organisation's system-level rules only, so a token with its own requirements can still refuse the user. On a network with an EVM identity registry it also shows the identity registration status, and to an identity manager or verification issuer it shows the KYC review status, such as “KYC review: Approved”. That is the reviewer's decision on the KYC profile, not the on-chain KYC verification a token checks. The tabs are “Overview”, “Holdings”, “KYC”, “Verifications”, “Roles & permissions”, “Wallets”, “Activity log” and “Security”. “KYC” shows to an identity manager or verification issuer, and “Security” to an identity manager. A user with no participant in this organisation shows a notice in place of positions and transactions.
The Account is the wallet that acts for the user. In an organisation that uses smart accounts, on a network that is ready for them, it is the user's smart wallet. Otherwise it is their signing key. The “Register identity” confirmation names the same address.
The Overview tab shows the user's facts, their top positions and last five transactions, and these panels:
- The KYC status of the user's profile, with a link to the KYC tab, for an identity manager or verification issuer.
- Access, with the organisation role and the system roles the user holds.
- Platform account, for a platform administrator only, with the user's platform role, sign-in state and a link “Open in Platform users”.
- Global eligibility, described in Read the global eligibility verdict.
- The identity's verifications, with a link to the Verifications tab and Verify a participant.
- User setup checklist, for an identity manager or verification issuer, which lists the open steps: “Create identity on-chain”, “Register in the identity registry”, “Issue KYC verification” once the profile is approved and no KYC claim exists, “Update KYC information”, and “Re-issue KYC verification” after the profile changed. On a Canton network it also lists “Allocate party on the network”.
The Wallets tab lists the user's wallets, and Restrict a wallet covers the restriction actions on its cards. The “Roles & permissions” tab shows the organisation role and the system and asset roles held by the user's wallets, and Change a user's organisation role covers the button on it.
Register a user's identity
On a network with an EVM identity registry, the header shows one identity action once the Console has looked up the account's identity. Create identity shows when the wallet has no identity contract. It deploys one for the wallet on the network in view, and the page moves to the next state on its own once the indexer records it. “Register identity” shows when the identity contract exists but is not registered. It opens the registration sheet, where you choose the country recorded for the wallet and confirm with your transaction PIN or transaction code. Country allow and block lists read this registration country, not the KYC profile's country. Both actions are enabled for an identity manager and disabled with a reason for other accounts. Once the identity is registered, neither shows.
Until registration completes, the user can sign in and receive roles but cannot hold or receive a regulated token, because every token checks the identity registry before it moves a balance. Registration alone is not eligibility: a token that requires a verification, such as KYC, still refuses the wallet until a trusted issuer adds it. Verify a participant covers that step, and Onboard an investor follows the whole sequence from first sign-in to a verified holder.
For a registered user, the identity card on the Overview and “Verifications” tabs offers “Change country” and “Remove registration” to an identity manager. “Remove registration” asks “Remove this registration?” and your wallet verification. It takes the wallet out of the identity registry, so the wallet can no longer receive tokens that check the registry until it is registered again. The identity contract and its verifications stay on the ledger. To stop a wallet without removing its registration, use Restrict a wallet.
Review a user's KYC profile
A user's KYC profile is the know-your-customer record the organisation keeps for them: first name, last name, country, national ID, the fields that profile sections add, and supporting documents. Each organisation keeps its own profile for a person. Changes collect in a draft version, and each submitted version stays in the profile's history. The investor fills it in from Profile in the Investor portal or the Console and selects Submit for review.
- Open the user, then the KYC tab. The “Users” list filters by KYC status, and the dashboard shows “3 KYC profiles await review”, with the current count, when profiles wait for a decision.
- Read the profile card, its fields and documents, and the versions table, which lists the versions that reached review with their status.
- Select a version in the table to read it, then decide it with Approve, “Reject” or “Request update”. Each opens its own page under the user's “KYC” tab, with a breadcrumb back to the tab and “Cancel” to return without deciding. “Approve” takes optional notes. “Reject” needs a reason of at least 10 characters, which the investor sees. “Request update” sends the investor a message of at least 10 characters and opens an action for them in the Console or Investor portal. After the decision the Console returns to the “KYC” tab.
- On the profile card, an identity manager can also approve every field with Approve all, ask for changes on named fields with “Request changes”, or correct a field and select “Save”, which leaves the version for another reviewer to approve.
The person who submitted or corrected a version cannot approve, reject or request an update on it, and the Console hides those buttons for them. When a platform administrator submitted or corrected the version while impersonating the member, that administrator cannot review it either. A correction an identity manager saves waits for a different reviewer, an identity manager or verification issuer who did not edit the version, to approve it. An owner who is the organisation's only reviewer needs a second one before their own profile can be approved.
The platform refuses an approval that would leave a required field empty, or a field that still needs changes, and writes nothing. The investor receives an email with the outcome when the platform has mail delivery and the user has an email address. Audit trail lists the operations the platform records, with who performed each one and their role at the time, and records each opening of a participant's KYC record as a sensitive read.
Approving a profile does not issue the on-chain KYC verification. The overview checklist then shows Issue KYC verification, and a verification issuer adds it from Verify a participant. Only an issuer that Trusted issuers lists for the topic adds a verification a token accepts. When the identity is registered and the approved profile has a country, the approval does add a Residence verification for that country, issued by the organisation's identity.
Read the global eligibility verdict
Global eligibility says whether the user passes the organisation's system-level compliance rules on the selected network: “Eligible”, “Needs action” or “Blocked”. It lists each reason, such as “Wallet is on the global address blocklist.” or a missing, revoked or expired required verification (a verification whose issuer is not trusted for its topic counts as missing), and links to “Compliance › Global controls” or “Verifications” where you fix it. A user with no wallet shows “No wallet on file. Eligibility cannot be evaluated yet.”
The verdict first comes from indexed data and is marked From indexer. Select “Recheck now” to run a live check on the network. The live result replaces the indexed one and is marked “Live check”. When the live check times out, the tile keeps the indexed verdict, marks it “Live check” and adds “Live check timed out for one or more modules.” Read the verdict after a timeout as the indexed one. The verdict covers the organisation's global controls only. Whether the user may hold a particular asset, or make a particular transfer, depends on that token's own check.
Change a user's organisation role
The Roles & permissions tab opens with an “Organisation” card that shows the user's “Organisation role”, “Owner role ends” when the owner role has an end, and “Member since”. An organisation owner sees “Change organisation role” on the card. The button does not show to other accounts.
- Select Change organisation role. A dialog opens.
- Under Organisation role, choose “Member” or “Owner”. “Member” “Reads the organisation's settings.” “Owner” “Changes settings, invites people, removes members and changes roles.” The current role carries a “Current” badge.
- For Owner, optionally set “Owner role ends”. At that time the platform returns the user to member. Leave it empty to keep the owner role until someone changes it. The end must be at least two minutes away, and the field does not show when you change your own role.
- Select Save role.
When you change your own role to Member, the dialog warns that you can then no longer change settings, invite people or change roles. The card also lists the system and asset roles the user's wallets hold. They are read-only here, and “Manage roles” opens Roles and permissions for an account that may grant them. You change an on-chain role there.
Manage a user's security
The Security tab shows to an identity manager. Its cards show the user's wallet address, “Sign-in code”, “Transaction PIN”, “Transaction code” and “Active sessions”, with the count of sessions and, for each session, the device, the IP address, when it was last active and a “Revoke” button. Below them:
- Reset credentials sends the user a password reset email. It shows only when email is configured and the user has an email address. The email says that an administrator of your organisation started the reset, names your organisation, and tells the user to contact an administrator of your organisation if they did not expect it. It is sent in the user's language, and it does not say the user asked for the reset.
- Unlock user clears the user's password lockout after repeated wrong passwords.
- Identity recovery replaces a lost or compromised wallet and cannot be undone. “Recover identity” creates a new wallet and deploys a new on-chain identity, moves the user's tokens to the new wallet, revokes all their sessions and resets their sign-in code, passkeys, transaction PIN, transaction code and recovery codes. Their password and API keys stay. Verifications from your organisation's own issuer are reissued, and other issuers must reissue theirs. It is unavailable until the user has a wallet address, and it restores an EVM identity contract only. A recovery waits for another owner or administrator of the organisation to approve it, because the “Recovery” group under Approvals starts on. An owner turns that group off to let one identity manager recover a wallet alone. Recover a user who lost their wallet gives the steps.
The danger area at the foot of the tab holds Reset sign-in code, “Reset transaction PIN”, “Revoke all sessions” and, for an organisation owner, “Remove member”. Each of the first three asks you to confirm with your transaction code, or with your transaction PIN when you have no transaction code, and has a button to keep things as they are: “Keep sign-in code”, “Keep PIN” and “Keep sessions”.
- Reset sign-in code removes only the authenticator app the user signs in with. Their transaction PIN, transaction code, recovery codes and sessions stay. The user sets up a sign-in code again from their own Security page.
- Reset transaction PIN removes the user's PIN and signs them out everywhere. They set a new PIN after signing in, and their recovery codes and transaction code stay. The platform emails them about the reset, and the organisation's cooling-off period holds their signing.
- Revoke all sessions signs the user out of this organisation on every device.
An action is unavailable, with its reason shown, when there is nothing to reset: No sign-in code set up, “No transaction PIN set” or “No active sessions”. On your own account the reset and revoke actions are unavailable with “Manage your own security from your Security page.” and “Remove member” does not show.
Remove a member
Removing a member cannot be undone. It removes the user from the organisation, revokes all their sessions, and cancels the approvals the member started and the approvals waiting on them as checker. It cannot revoke a role on chain, so the platform refuses to remove a member while a wallet they act or sign with still holds a system role or a role on one of the organisation's assets. The user's Roles & permissions tab lists the system and asset roles their wallets hold. Revoke them first in Roles and permissions and on each asset's “Permissions” tab. The identity registration and the wallet's holdings stay.
Remove member is in the danger area of the “Security” tab. It shows only to an organisation owner, and never on the owner's own account. While the member holds a system role, it is unavailable with “Revoke this member's system and asset roles first. A role stays active on chain after the member leaves.”
Select it, read “Remove member from organisation?”, and confirm with “Remove member”, or select “Keep member” to stop. The Console does not check asset roles, so when the member still holds one, the removal fails with “The member still holds on-chain roles” and the member stays. The Console returns to the “Users” tab after a removal.
View a user in My participants
The user's header has a View in my participants button when the user's participant is one you may act for. It opens that participant's page under “My participants”. My participants describes that screen.
Refresh your own ENS avatar
An identity manager who opens their own user page sees Refresh the ENS avatar in the header when the deployment has ENS available. It reads the ENS avatar of each of your participant's wallets again. An ENS avatar is the image a wallet owner publishes through the Ethereum Name Service. A wallet can be refreshed once every ten minutes, and inside that window the control says “Available again in about 4 minutes.”, with the remaining minutes. When nothing new is stored, the control says why, such as that the address has no ENS avatar or that the hourly avatar budget is spent.
Columns on the Users tab
The Type column shows the first match in this order: “Pending” while a user's roles are still being set up, “Admin” for an administrator or a holder of the permission manager or system manager role, “Trusted issuer” for a verification issuer, “Asset manager” for a token manager, and “Investor” for everyone else. “Identity registration” reads “Registered” when the user's identity is active in the system's identity registry and “Registration pending” otherwise, including for a user whose wallet has no identity. The column's filter calls the second state “Pending registration”. A user with no wallet on the selected network shows no status. The “Country” column shows the country of the user's KYC profile. When the profile has no country, it shows the country recorded at identity registration, marked “From registration”. The country filter and sort read the KYC country only.
Troubleshooting
Access restricted
Your account holds none of the System manager, “Identity manager” or “Verification issuer” roles, and you are not the organisation owner. Ask a permission manager for one of the roles in Admins and roles.
Create user is refused because no custody provider serves the network
The organisation has no managed custody provider for the active network, or the providers could not be read. An administrator enables one in Custody. Invitations still work, because the invitee sets up their own wallet when they accept.
The toast says the custody account is still settling
“User created. Their custody account is still settling and is not usable yet.” means the user exists and the managed wallet is still being provisioned. Do not register the identity or create the user again until the custody account has settled.
An invitation shows Accepted, roles not granted
The invitee joined, but the on-chain roles on the invitation could not be granted. Check the user's roles, and grant the missing ones in Roles and permissions.
Copy invitation link says the invitation has expired
“This invitation has expired. Resend it to send a new link.” An invitation that expired while pending shows the status “Expired” and keeps its row actions. Select Resend invitation, or cancel it with “Cancel invitation” and send a new one. Cancelling cannot be undone.
Approve is missing on the KYC tab
You submitted this version yourself, the version is not under review, or it is not the latest version. Ask another reviewer to decide it.
The country reads From registration
The user has no country on their KYC profile, so the list shows the country recorded at identity registration. The country filter reads the KYC country only, so this user does not match a country filter until their profile has a country.