A member is a user who belongs to the organisation. From a user's page in Users, an organisation owner changes the member's organisation role on the Rights tab, an identity manager resets the member's sign-in code, transaction PIN and sessions on the “Security” tab, and an owner who is also an identity manager removes the member and takes back the on-chain roles they hold. An owner with no on-chain role cannot open a user's page and changes the role from the member's row menu on the “Invitations” tab, which also offers “Remove member”.
Change a user's organisation role
“Change organisation role” is in the member's row menu on the “Invitations” tab and on the “Organisation” card of the user's Rights tab. The card shows the user's “Organisation role”, “Owner role ends” when the owner role has an end date, and “Member since”. The button shows only to an organisation owner.
- Select Change organisation role in the member's row menu or on the card. A dialog opens.
- Under Organisation role, choose “Member” or “Owner”. The dialog describes “Member” as “Reads the organisation's settings.” and “Owner” as “Changes settings, invites people and changes roles. Removing members also needs the Identity manager role.” The current role carries a “Current” badge.
- For Owner, optionally set “Owner role ends”. On that date the platform makes the user a Member again. On the card, leave it empty to keep the owner role until someone changes it. The end date must be at least two minutes away, and the field does not show when you change your own role. When you open the dialog from the “Invitations” tab for an owner, the field starts empty even when the owner role already has an end date, because that tab does not load it, and the hint under the field says so. A date you set there replaces the end date, and an empty field keeps it. Only the card shows the current end date and can remove it.
- Select Save role.
While the organisation protects the Role management group, the change waits for another owner or a platform administrator to approve it in Actions, as an invitation does. The platform refuses to change the organisation's only owner to Member. Changing an owner to Member, here or when their owner role ends, cancels the pending invitations they sent, as removing them does. Audit trail records each change, with who made it and the role before and after.
When you change your own role to Member, the dialog warns that you can then no longer change settings, invite people or change roles. If you made the change on the Invitations tab, the Console then opens the Users tab, or shows that access is restricted when you cannot list users. 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 the authenticator app the user signs in with. It also deletes the user's API keys for this organisation and disconnects the AI apps they connected to it through the hosted MCP server, which they then connect again. 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. It also deletes their API keys for this organisation and disconnects the AI apps they connected to it through the hosted MCP server. 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, and ends every session of theirs that has no organisation selected. It deletes the user's API keys for this organisation and disconnects the AI apps they connected to it through the hosted MCP server. The button is unavailable while the user has no active session here, so for a signed-out user it ends no key or app.
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.
You act on a user who ranks at or below you. An owner ranks above a platform administrator, and a platform administrator ranks above a member. The user is ranked on their highest role in any organisation they belong to that is not archived, so a member here who owns another organisation ranks as an owner. An identity manager who is a member can therefore act on other members, but not on an owner, a platform administrator or a member who owns another organisation. For a user who ranks above you, reading their security, profile or KYC profile and every action in this section, including Reset credentials, “Unlock user” and the “Revoke” button on a session row, fail with “Another owner must act on this member” and nothing changes. A change to their participant status ranks the user on their role in this organisation alone, so a member here who owns another organisation can still be suspended by an identity manager who is a member. The platform refuses an identity recovery for a user who ranks above you. The platform checks this before it asks for your transaction code or PIN.
The user's details, sign-in code, transaction PIN, sessions, password, sign-in lockout, participant status, profile, KYC profile and identity recovery belong to the user's account, not to one organisation. When the user also belongs to another organisation that is not archived, opening the user, reading their security, profile or KYC profile, Reset sign-in code, “Reset transaction PIN”, “Revoke all sessions”, “Revoke” on a session row, “Reset credentials”, “Unlock user” and an identity recovery fail with “Only the member can manage this account”, because they would reach every organisation the user belongs to. The user makes the change from their own Security page, or an owner removes them from this organisation. A participant status change is the exception: it reaches only this organisation's subscriptions of the user, so it works for a user who belongs to another organisation too.
Remove a member
Removing a member cannot be undone. It removes the user from the organisation and revokes their sessions in it. It deletes their API keys for the organisation and disconnects the AI apps they connected to it through the hosted MCP server. It also cancels the pending invitations they sent, the approvals the member started and the approvals waiting on them as checker. The identity registration and the wallet's holdings stay. When the user is added back later, they approve each AI app again before it works.
A role on chain keeps working after its holder leaves, so the platform takes back the member's on-chain roles before it removes them, and a removal takes two passes. The first request starts the revoke of every role the platform can revoke and is refused while a role remains. A later request removes the member once the platform's record of the chain shows no role the removal covers. A role the platform leaves in place, such as one on a wallet another person also controls, stays until someone revokes it by hand in Roles and permissions or on the asset's “Permissions” tab. Roles of a person who leaves lists the wallets and roles a removal covers, and each reason the platform leaves a role in place.
The platform sets your wallet as the signer of an asset or trading venue revoke when your wallet administers the role and the platform manages its key, and the organisation's operations signer otherwise. When that wallet can no longer revoke the role at the moment the revoke runs, the platform signs with the operations signer instead. It never signs with the wallet set on another open time-bound grant of the same asset or venue, because that wallet can belong to another member or to the person who leaves.
On a system that several organisations share, the removal covers only the tokens and trading venues your organisation issued. It covers the system roles and the add-on roles there, such as a custody gateway's or a token sale's, only when the member belongs to no other organisation on that system. A ban, a closure or a delete by a platform administrator covers the other organisations' roles too. The platform never revokes a role on an add-on other than a trading venue. A covered add-on role holds the removal back until someone revokes it by hand where that add-on's roles are managed, such as the “Add-on roles” tab of Roles and permissions for a custody gateway.
In the Console, revoke the member's system roles by hand first, because “Remove member” stays unavailable while the member holds one. The platform's own revokes then cover the member's asset and trading venue roles. Through the Platform API, the removal revokes the system roles too. The user's Rights tab lists the system and asset roles their wallets hold. API routes gives what each answer of the removal says about the roles.
Remove member is in the danger area of the “Security” tab, and in a member's row menu on the “Invitations” tab. It needs an owner role with no end date and the “Identity manager” role on the wallet you act with, and it never shows on your own account. On both tabs, while the wallet you act with does not hold the “Identity manager” role, it is unavailable with “Removing a member also needs the Identity manager role. A Permission manager can grant it.” When it holds that role, it is unavailable with “Revoke this member's system and asset roles first. A role stays active on chain after the member leaves.” while the member holds a system role. On the “Invitations” tab, until the Console has read which members hold a system role, it is unavailable with “Removing waits until this member's system roles have loaded. Reload the page if it stays unavailable.”
Select it, read “Remove member from organisation?”, and confirm with “Remove member”, or select “Keep member” to stop. When the member holds an asset or venue role, the platform starts the revokes and refuses this first request with “The member still holds on-chain roles”, and the member stays. This refusal is expected. Reload the user's Rights tab until the asset roles are gone, a few moments after their transactions confirm, then remove the member again. The “Rights” tab does not list add-on roles: when the removal is still refused, look for them on the “Add-on roles” tab of Roles and permissions, or read every role through the Platform API, as the troubleshooting below says. The platform also refuses to remove the organisation's only owner.
While the organisation protects the Role management group, each removal request waits for another owner or a platform administrator to approve it in Actions. The revokes start when the approved removal runs, so a member with roles takes two approved requests. After a removal from the “Security” tab, the Console returns to the “Users” tab. After a removal from the “Invitations” tab, it stays on that tab, and the member's “Joined” row leaves the list once the removal takes effect. Audit trail records each removal, with who removed the member and the organisation role the member held.
Troubleshooting
Remove member is unavailable
The reason under it says which rule applies. “Removing a member also needs the Identity manager role.” means you do not hold that role, and a Permission manager grants it in Roles and permissions. “Revoke this member's system and asset roles first.” means the member still holds a system role. Revoke it in Roles and permissions, then remove the member. “Removing waits until this member's system roles have loaded.” means the Console is still reading them, or the read failed. Reload the page.
The removal fails because the member still holds on-chain roles
A wallet of the member still holds a role the removal covers. The platform has started the revokes it can make. Wait
until the user's Rights tab no longer shows the roles, then remove the member again. When the removal still fails,
the platform leaves a role in place, such as an add-on role or one on a wallet another person also controls. Read the
roles and their reasons through GET /api/, and Roles of a person who
leaves says what to do for each
reason. Revoke those roles in Roles and permissions, on its
“Add-on roles” tab for a custody gateway, or on the asset's “Permissions” tab, then remove the member again.
API routes
The API v2 reference holds the request and response schemas.
DELETE /api/removes a member. While a role the removal covers remains, it answersv2/ organizations/ members/ {user Id} 409 ConflictwithPLATFORM_and lists each role inMEMBER_ HOLDS_ ROLES data.roles, asrevokingor asnot-revocablewith itsreason. A removal that goes through returnsdata.offboardingwithstatusstartedand emptyrevokingandremaininglists, unless the person keeps roles for another organisation on a shared system: those readnot-revocablewithheld-, do not hold the removal back, and stay in place. If that organisation's owner removes the same person at once, the second removal answers like a single removal:for- another- organization 409 Conflict, listing the system roles it now revokes. When a revoke could not be started, it answers503 Service Unavailablewithplatform.and removes nothing. When the platform read every role the removal covers, that answer carrieshttp. DEPENDENCY_ UNAVAILABLE data.offboardingwithstatusfailed:revokinglists the roles being revoked, andremaininglists the roles the platform leaves in place, each with itsreason, and the roles whose revoke did not start, with noreason. When it could not read them, the answer carries nodata.offboarding, so read the roles through the route below once it answers again. The revokes that did start go on, and you send the request again in a moment to start the others. For a non-member of the active organisation, it answers404 Not FoundwithPLATFORM_, and nothing is revoked.MEMBER_ NOT_ FOUND GET /api/lists the roles a removal covers before you send it, each with itsv2/ organizations/ members/ {user Id}/ roles stateand, for a role the platform leaves in place, itsreason. It needs an owner of the active organisation, and answers404 Not Foundfor a user who is not a member. Read it again after a refused removal to follow each role until it is gone.