A person's account status says what they may still do in your organisation: “Active”, “Restricted”, “Suspended”, “Closed” or “Terminated”. Each wallet the person holds in the organisation carries its own status, and the person's status is the strictest one in force. On “Change account status” you set a new status on every wallet at once, or on one wallet, with a reason that stays in the status history. The page shows which wallets the change reaches, which it leaves alone and why, and refuses a change that would leave the organisation without an owner or a role holder before anything is written.
“Resume account” ends a suspension. Each suspended wallet gets back the status it had before it was suspended, so a wallet that was “Restricted” before is “Restricted” again. A status set here applies only in this organisation. A person's wallets in another organisation keep the status set there.
The “Change account status” page for a person in the organisation.
Steps
Open the person
Open “Organisation participants”, then “Users”. An identity manager sees an “Actions” column in the list: open the row's actions and select Change status. Or open the person, then the “Rights” tab, and select “Change status” on the “Account status” card. Either way the change applies to every wallet the person holds in this organisation.
To change one wallet only, select Change status in that wallet's row of the “Wallet statuses” table on the “Rights” tab. The page then reads “Set the account status on one of this person's wallets in this organisation.”
Choose the new status
Under New status, choose “Active”, “Restricted”, “Suspended”, “Closed” or “Terminated”. For “Restricted”, tick at least one function under “Restricted functions”: “Trading restricted”, “Securities transfers restricted” or “Withdrawals restricted”. Every other function stays available.
Read what the change reaches
Once you choose a status, the page checks the change before you make it. It names each wallet it changes, as “Changes 2 wallets” with their addresses, and each wallet it leaves as it is, with the reason:
- “because it already has this status”, for a wallet that holds the new status already.
- “because terminated is final”, for a wallet that is terminated. A terminated wallet never changes again.
When the change is not allowed, the page shows “This change is not allowed” with the reason, and Change status stays disabled. What the platform checks lists the reasons. When a multisig wallet would lose the signer seats it needs, the page shows “Multisig wallets need this person” and still lets you make the change.
Set when it applies
Leave Effective from empty to apply the change now. Choose a later date and time to schedule it: the status history shows the change as “Scheduled” until then. A new change replaces a change still scheduled on the same wallets, and the history shows the replaced one as “Cancelled before it took effect”.
Record the reason
Choose the Reason from the reason codes, and write the “Note”, up to 500 characters. Both are required, and both stay with the change in the status history.
Change the status
Select Change status. When it is disabled, the line beside it says what is missing, such as “Choose a reason.” or “No wallet would change.”. Wait for “Account status changed”. The Console returns to the “Rights” tab, where the “Account status” card and the “Status history” table show the change.
Resume an account
Resume shows on the “Account status” card when at least one of the person's wallets holds a suspension of its own. In the “Users” list it shows as “Resume account” in the row's actions, and in the “Wallet statuses” table as “Resume” on a suspended wallet.
“Resume account” names the wallets it resumes, as “Resumes 2 wallets”. Choose the Reason and write the “Note”, then select “Resume”. A resumption applies now, and each suspended wallet gets back the status it held before its suspension, with its restricted functions. A wallet that had no status of its own before it was suspended gets back the strictest status the person's other wallets held then, which is the status it inherited, or “Active” when none held one. A change still scheduled on a resumed wallet is cancelled. Venue orders the suspension cancelled stay cancelled.
A resumption reaches only wallets with a suspension of their own. A wallet that shows “Inherited from another wallet” takes its status from the person's other wallets, so it changes when they do. When no wallet holds a suspension of its own, the page shows “Nothing to resume” and “Resume” stays disabled.
Reason codes
What the platform checks
The page checks the change when you choose the status, and the platform checks it again when you submit, so a change that became unsafe in between is still refused. The checks run before anything is written. When the platform cannot read what a check needs, it refuses the change, and the page shows “The Console could not check what this change reaches. Try again.”
A role counts as held by someone else only when that person is not suspended, closed or terminated in the organisation themselves.
Where the status takes effect
The platform checks the status of the wallet that acts, in the organisation where it acts. “Active” stops nothing. “Suspended”, “Closed” and “Terminated” stop all three functions below, and “Restricted” stops only the functions you ticked:
A trading venue also reads the status when it admits a wallet, and a “Suspended”, “Closed” or “Terminated” status cancels the wallet's open orders on this organisation's venues within about a minute of taking effect, as Participant access describes. Custody gateway review and Cash-outs describe how a withdrawal or cash-out shows the refusal. Tokens on Canton do not check the status yet.
What reaches a wallet that cannot receive
While a wallet is “Suspended”, “Closed” or “Terminated”, nothing can be sent to it in this organisation: transfers, mints, token sale purchases and deliveries, settlements and conversions to it are refused, and a corporate action run skips it. Forced transfers, refunds and burns stay open. A bank payment or gateway deposit for the user is held until the status is active again or returned, and a stop order naming the wallet is cancelled when it triggers.
The platform refuses these calls itself, and the status freezes nothing on chain. To freeze a wallet on the tokens it holds, restrict the wallet.
Troubleshooting
Change status is not offered
Only an identity manager sees Change status and “Resume”. Ask an owner to grant you the “Identity manager” role. A person with no wallet in this organisation has no status to change.
The page says This change is not allowed
Read the reason under the title. For the only holder of a role, grant each role it names to another person who is not suspended, closed or terminated and has no such change scheduled, then open the page again. For the last owner, make someone else an owner first, or resume an owner who is suspended.
Change status stays disabled with No wallet would change.
Every wallet already has the status you chose, or is terminated. Choose another status, or close the page.
Resume does not show for a suspended person
No wallet holds a suspension of its own in force. A wallet whose “Source” reads “Inherited from another wallet” changes with the person's other wallets, and a suspension still “Scheduled” cannot be resumed before it takes effect. Change the status instead, or wait until the suspension is in force.
API routes
The Console calls the participant status operations of the Platform API: GET /api/ to check a change, POST /api/ to make it and POST /api/ to resume. The Platform API reference lists every field and response, and Upgrade to DALP 3.2 describes how they changed.