Organisation participants
Manage everyone the organisation tracks an identity for: users with a login, entities without one, saved contacts, and the verification records a token checks.
Every regulated token checks the On-Chain IdentityAn On-Chain Identity lets a subject's verification serve every asset that accepts it, so a screened wallet skips re-onboarding for the next regulated asset.Read the concept records this section tracks before it lets a wallet hold or move value, not the Console's own login system. Users and Entities list registered people, accounts, and contracts. Contacts is a separate address book; saving a contact creates no identity.
Users, Contacts, and Entities have separate purposes and access checks. Users and Entities each gate their own roster behind a list permission; Contacts is the one page here with no permission gate at all, so any account onboarded to the organisation can add, edit, and delete its own contacts.
Choose a roster or the address book
Users and Entities
Both write to the same on-chain identity record that a regulated token reads before it lets a wallet hold or move value. Registering a participant here is what makes it checkable at all, and each page gates that registration behind its own permission, separate from the permission that lets you view the roster.
Contacts
A name paired with a wallet address, private to the account that saved it. Saving one creates no identity and runs no compliance check; every operation that later uses that address still runs its own independent check, exactly as it would for an address typed in by hand.
In the sidebar itself, Users and Entities sit inside one group gated on the admin, identity manager, or verification issuer role: an account with none of the three loses both items together. An account with the admin role but neither of the other two still sees the group, with Users and Entities rendering disabled and a tooltip explaining the missing role. Insights is not a sidebar item: it is the "Insights" tab beside "All users" on the Users page, shown to an account with the admin, identity manager, or verification issuer role. Contacts sits in its own "User settings" group, which every onboarded account sees.
The other two pages are not a fourth and fifth kind of participant; they describe the registered participants and their claims. Insights reads it, and Verify a participant proves one participant against it, inside Transfer-Path ComplianceTransfer-Path Compliance enforces a regulated token's rules inside the on-chain transfer itself, so a movement that fails any rule reverts and never settles.Read the concept: the transfer enforces the current rules when it executes. A successful preliminary check does not reserve eligibility.
Everything on these pages is about someone or something other than your own signed-in account. Use your account menu to manage your profile, know-your-customer (KYC) submission, security, and API keys. Open Acting as participants to choose which participant your work applies to. That page switches which participant you act for; this section's Users, Contacts, and Entities pages manage the organisation's roster of participants and counterparties as a whole, regardless of who is currently signed in.
Governance votes
Governance votes are the Console workflow for creating an on-chain vote, casting ballots on it, and carrying out whatever a token's holders approved.
Users
Manage organisation participants with login credentials, wallets, on-chain identities, roles, and invitations, and review a user's holdings and eligibility.