Acting as participants
View every participant you can act for, switch which one your actions apply to, and create a new participant when your organisation needs one.
Acting as participants is where you see every ParticipantA participant lets every role grant, claim, audit row, and delegated action point at one stable subject, so a person's history never splits.Read the concept you can view, manage, or act for, and switch which one your wallet work applies to. Your own account is a participant, and so is every other wallet, person record, or organisation record shared with your account. Switching does not change what you personally may do; it changes whose identity, holdings, and pending items you are looking at, and on whose behalf you sign a transaction. This split is Delegated AuthorityDelegated Authority lets a signed-in operator work inside another party's account. One check decides who may enter; the party's own roles decide the rest.Read the concept: your own entitlement decides which participants you may enter, and each participant's own roles decide what happens once you are acting for it.
Reach for this page when you need to view or transact for a wallet that is not your own, or when your organisation needs to provision a new participant. Come back here too when a participant your organisation controls needs registering somewhere new, or when one is missing its identity contract and needs recovery.
An EOA, a single-sig, or a multisig provisions differently
Every new participant needs a wallet type before it can do anything. Your organisation only offers the choice at all when account abstraction is turned on; otherwise every new participant is an EOA, and no picker appears.
| Wallet type | Choose it when | What you get |
|---|---|---|
| EOA | Your organisation does not need smart-account features for this participant. | A wallet address with no smart-account features. |
| Single-sig smart account | One key should control the participant, provisioned as a smart account rather than a bare key. | A single-key smart account, provisioned through your organisation's bundler and paymaster. |
| Weighted multisig smart account | More than one party must agree before a transaction executes. | A smart account that signs once its seated signers reach the threshold. |
A wallet participant's wallet type is fixed at creation. Nothing here, or anywhere else, converts an EOA into a smart account or a single-sig into a multisig afterward; correcting a wrong choice means creating a new participant, and the old one keeps its own history. A person or organisation participant never carries this choice at all, since you do not create either through this flow.
A multisig also carries its own path from confirmation to a working wallet, and part of that path happens outside Console entirely: an invited signer joins by opening a link you send them, not by clicking anything here.
A multisig draft opens with its creator as the first signer, more signers join by account, invite, or address, and it can finalize only once the threshold is reachable with nothing left pending. The creator can delete an open draft instead, at any point before it finalizes.
Steps
Open the participant switcher
Open the account control in the Console's top bar. It shows your avatar and name, or, while you are already acting as someone else, a two-part control naming both your own account and the participant you are currently acting as. Its Acting as section offers Switch; select it to expand an inline list, then select View all to open the full participants table. The table lists every participant you can view or manage, with columns for Name, Type, Your role, Identity address, Status, and Actions, plus an Acting badge on whichever one is currently active.
Screen equivalent: a table of participants with kind, identity on the selected network, and a row menu offering Set active and, where eligible, Register in organisation, plus a Create participant button.
Switch the active participant
Open the row menu for the participant you want and select Set active. The Console reloads participant-scoped views for the selected participant. Check the Acting as label before reading holdings or submitting an operation; your personal account settings and active organisation retain their own scope.
Create a participant
Select Create participant, name it, and choose an available custody configuration. When your organisation has account abstraction enabled, choose a wallet type using the guidance above; when it does not, every new participant is an EOA and the picker does not appear. An EOA or a single-sig participant provisions once you confirm, though its custody account can still be settling behind the scenes. When that happens, Console reports "Participant created. Its custody account is still settling and is not usable yet". For self-custody, follow the instruction to prove control of the wallet. A participant waiting for that proof does not become usable through waiting alone.
A weighted multisig provisions differently. Pick which of your own eligible accounts becomes its first signer, using the Signing account picker, which shows No eligible signing accounts if you have none. Confirming opens a draft, still nothing on-chain. Add the rest of its signers there: an existing account of your own (set its signing weight before you add it), a platform account by email invite, or a bare external address that never has to accept anything. Then set its threshold; leave it unset and the draft deploys requiring every seated signer to sign.
Finalize & deploy becomes available once the assembled signer weight, including any external address, can reach that threshold and no invite is still pending. That check is not the same as asking whether you can actually collect that much weight. An external address counts toward the threshold without ever having to sign through Console, so the assembled weight can clear the gate while the accounts you and your invited signers control cannot reach the threshold alone. Console warns rather than blocks when that happens, so add more of your own or invited signers before you finalize if the warning appears.
Finalize & deploy is the step that deploys the multisig on-chain for good, and it too can leave a custody account still settling. When that happens, Console reports "Multisig participant deployed. Its controlling custody account is still settling". The multisig stays unusable until that finishes.
Troubleshooting
Set active is disabled with a tooltip I do not understand
The three reasons are distinct. A participant with no wallet at all was never provisioned with one and needs attention outside this page. One with a wallet but no on-chain identity contract can recover through its own identity tab. One missing a smart wallet, under an account-abstraction wallet type that has not finished provisioning, needs its own follow-up, separate from the identity case.
A participant I manage has no identity contract
Identity provisioning is a separate step that runs right after a participant is created, and a transient failure can leave a participant stranded without a contract even though the participant record itself exists. Open that participant's identity tab; it shows an explanatory message with a recovery button that provisions the missing identity. Anyone authorized on the participant's own wallet can use it, whether or not they are currently acting as that participant.
I'm stuck adding signers to a multisig draft
Two different gates cause this. If the Signing account picker shows No eligible signing accounts and will not let you continue, you have no EOA or single-sig participant of your own in this organisation yet. Create one first, then start the multisig again; it becomes the first signer.
If you already have signers seated but Finalize & deploy stays disabled, an invite is still pending. It resolves when the person you invited opens the link outside Console and joins, or when you revoke it, but it does not resolve on its own. An invite link expires after a while, and an expired invite still counts as pending, blocking Finalize & deploy until you revoke it, even though its row keeps showing Invited with no expiry shown.
For an expired or lost invitation, revoke it and send a new one. A valid pending invitation can still be accepted; check with the signer before replacing it. An invite link is shown once, at the moment you create it, so revoke and re-invite rather than trying to recover a lost one.
I need a participant registered in another organisation
Act as the participant first, then open its row menu and select Register in organisation, if it appears. It only appears on the participant you are acting as, and only when there is an organisation left to register into: one you belong to where this participant is not yet active. An organisation holding only a pending registration stays in the picker, so a finalized multisig, which registers itself pending in its own organisation, is still offered that organisation until the registration is active. The request goes to that organisation's identity managers, who accept or reject it under Pending registrations; after a rejection you can ask again.
A participant I expect to see is missing from the table
This table only lists participants shared with your account, not every participant that exists. Ask whoever manages that participant's access to share it with your account; this page has no control that grants access to a participant you cannot already see.
Can I undo creating a participant or registering it in an organisation?
Almost never, with one exception. A multisig still in draft, before you finalize it, can be deleted by its creator, which removes it entirely and leaves nothing behind. Once you confirm a registration, or finalize and deploy a multisig, there is no button here that reverses it. Creating any other participant is one-directional the same way, and this page has no delete or archive control for one that already exists. Decide the organisation and the wallet type before you confirm, since reversing either afterward means asking whoever administers that organisation's registry, not something you can do from here.
I switched to another participant and want to return to myself
Open the account control in the Console's top bar. While you are acting as someone else, its Acting as section carries Return to yourself next to Switch. Select it and Console sets your own participant active again in one step. Confirm that the header now names your own participant.
Frequently asked questions
Can I act as two participants at the same time?
Not from Console browser tabs, since they all share one active participant for the session. Acting as two at once needs the Platform API instead; see Delegated Authority for how a request names its own participant.
Does creating a participant make it the one I'm acting as?
No. Creating a participant only adds it to your list; it does not switch you to it. Open its row menu and select Set active once it is ready, the same way you would for any participant that was already in the table before you created this one.
What do the Type and Your role columns show?
Type shows what the row is: Person or Organisation for a participant you did not create through the flow above, or EOA wallet or Single-sig account for one you created with that wallet type. A weighted multisig you create also shows as Organisation, the same label the column gives an organisation record, so this column alone does not tell the two apart. Your role names why you can act for it at all: Owner on your own participant, and Identity manager or Admin on one you control through a role granted on its organisation.
Do I need to finish setting up a multisig participant in one sitting?
No. An open draft keeps its state as you go. A resume list on the create sheet lets you pick it back up in a later session exactly where you left off, still with none of its signers deployed until you finalize it. An invite you sent does expire on its own, though: it still counts as pending until you revoke it, so returning to a stale draft can mean revoking and re-inviting before Finalize & deploy is available again.