My participants lists every Participant you can work as and lets you switch which one your wallet work applies to. It is also where you create a new participant. Your own account is a participant, and so is every other wallet, person record or organisation record shared with your account.
Switching changes whose wallet you act for. Your entitlement decides which participants you may enter, and once you are in, the action runs with that participant's roles and the record names you as the person who acted. This split is Delegated Authority. Registering a participant in another organisation is on its participant page.
The “You” section lists your own identities, each with “Work as” and “Make my default”, or the “Your default here” and “Working now” markers on the one in use.
Below it, “Organisation and shared participants” shows the “No participants” empty state, and the Create participant button sits at the top right.
Steps
Open My participants
The account menu sits at the right end of the Console's top bar. Its button shows the active organisation's name, and under it your own name, or “Working as” followed by the participant's name while you work as anyone other than yourself. When the top bar is narrow, the button shows only the avatar. While you work as someone else, the button turns violet. Select it, then select My participants. This works from any screen, even when you have a single participant. In the same menu, “On-chain identity” opens the identity tab of the participant you work as.
When you can work as more than one participant, or while you work as someone else, the menu also has a Working as submenu. Point at “Working as” to open it. A card at the top names the participant you work as, with a “Search participants” field under it. While you work as someone else, “Return to yourself” comes next. Up to three participants you switched to recently in this organisation, in this browser, follow under “Recent”, then the others under “Participants”. A participant you cannot work as is dimmed, and selecting it shows why. The submenu leaves out multisig wallets: each one you sign for opens as its own account under “Shared accounts” in the sidebar. “View all participants” at the bottom opens “My participants”.
My participants lists your own identities under the “You” heading, then the participants you can work as under the “Organisation and shared participants” heading. That table has these columns:
- Name
- Type
- Your role
- Identity address
- Identity
- Actions
The participant you work as carries a Working now badge.
Switch the active participant
Select Work as on the row of the participant you want, or select the participant in the “Working as” submenu of the account menu. The Console reloads the page you are on for the selected participant. If that page cannot show for the selected participant, the Console opens the nearest parent page that can. While you work as anyone other than yourself, a violet “Working as” bar opens every page with the participant's name and “Return to yourself”. While that bar shows, Portfolio, Activity, search and role checks use the selected participant's wallets alone, so a screen your own role opens can be unavailable until you return to yourself. A multisig where you hold a signer seat is the exception: you keep opening it, reading its signers and co-signing its approvals through your own seat. Check that bar before reading holdings or submitting an operation.
Switching does not change your account settings or your active organisation. It does change the participant your API keys act for: a key request without an X-Participant header uses your current choice within 30 seconds.
To return to yourself, select Return to yourself on the violet bar, or in the “Working as” submenu. The Console sets your own participant active again in one step. The bar disappears, and the account menu button is no longer violet and names you.
Most action sheets start with a From line that names the account the transaction runs from. While you work as yourself it shows your name and “your own wallet”. While you work as someone else it shows that participant's name and type on a violet strip, and for a multisig wallet it adds the signer weight the wallet needs against its total signer weight, such as “needs 2 of 3”. When the sheet cannot load the participant, it says so and asks you to close the sheet and open it again.
When you work as a multisig wallet, the sheet also shows a How this is signed panel before the submit button. It says how many signatures the wallet needs and whether your signature is enough, shows how much of the threshold your signature covers, and lists each signer. Your own seat reads “You” and “signs now”. A signer the platform manages reads “asked to co-sign”, and an external address reads “signs outside the platform”. A wallet with weighted signers shows each signer's weight. When your signature is not enough, the submit button reads “Sign and request” followed by the number of co-signatures still needed, and the other signers co-sign from “Actions” before the transaction runs.
Make a participant your default
A person participant of yours that is not your default offers Make my default on its row. Once you select it, the row shows “Your default here”.
Create a participant
- Select Create participant. The “Add participant” sheet opens.
- Enter an optional Display name and choose a wallet type if the sheet offers one, as Choose a wallet type describes.
- Pick the Key that signs for the participant's wallet. The key list holds the custody providers your organisation set up for the active network, among those your deployment enables. Each key option names the provider its configuration was added as, followed by “(this organisation holds the key)” or “(the person holds the key)”.
- Select Create participant.
An EOA or Smart wallet participant provisions once you confirm, though its custody account can still be settling at the custody provider. When that happens, the Console reports “Participant created. Its custody account is still settling and is not usable yet.” When the person holds the key, the participant stays inactive until that person, its owner, connects the wallet and signs the proof of control.
The “Add participant” sheet shows an empty “Display name” field, the “Smart wallet” type selected and the “Key” picker.
Create a multisig participant
- Select Create participant and choose “Smart wallet with signers”.
- In the First signer wallet picker, pick which of your own eligible accounts becomes the first signer. The picker reads “None of your wallets can sign in this organisation” if you have none.
- Select Save draft and continue to open a draft. Nothing is on-chain yet. The Console reports “Draft saved.”, and the draft appears in the “Multisig drafts” section of “My participants”, where “Resume” opens its signer editor and “Delete” discards it after asking.
- Add the rest of the signers. Add one of your wallets adds an account of your own, after you set its “Signing weight”. “Add platform signer (invite link)” invites a person with a platform account. “Add external signer (address)” adds a bare address that never has to accept anything.
- Set the Threshold. Leave it unset and the draft deploys requiring every seated signer to sign.
- Select Create multisig · N of M, where N is the draft's threshold and M its seat count.
The invite dialog takes a signing weight and an optional delivery email. It shows the invite link once, so save it before you close the dialog. The invite lasts seven days, and you can revoke it while it is pending. After seven days unused, the invite expires: its row reads Expired with no weight, it no longer blocks “Create multisig · N of M”, and the wallet deploys without that seat. Clear the row with its remove button. An invited signer joins outside the create sheet, through the invite link you send them, which leads to an accept page in the Console.
Create multisig · N of M becomes available once the seated signer weight can reach the threshold and no invite is still pending. The check counts every seated signer's weight, including an external address that never signs through the Console. So “Create multisig · N of M” can become available while you and your invited signers hold too little weight to reach the threshold. The Console then shows a warning but does not block the step. Add more of your own or invited signers before you finalise.
“Create multisig · N of M” also waits for the Console to read the custody providers of the active network, because the new wallet's custody account is opened with one. If that read fails, the draft says “The custody providers could not be loaded, so the smart wallet cannot be created.” with a “Retry” button. If no custody provider serves the network, it says “No custody provider serves this network, so the smart wallet cannot be created.” Set up a custody provider for the network first.
Create multisig · N of M deploys the multisig on-chain, and the deployment cannot be undone. It too can leave a custody account still settling. When that happens, the Console reports “Multisig · N of M created. The custody account of its signer is still settling.” The multisig stays unusable until that finishes.
A multisig draft opens with its creator as first signer, can finalise once the threshold is reachable with no invite pending, and can be deleted by its creator before it finalises.
Choose a wallet type
The basic wallet type depends on your organisation, and you cannot change it from the sheet. It is “EOA”, an externally owned account, when advanced accounts are off, and “Smart wallet”, a single-key smart account, when they are on. Advanced accounts is the organisation setting that gives participants smart wallets.
When the Self-custody module is on for your organisation, the “Add participant” sheet also offers “Smart wallet with signers”, a weighted multisig. It needs advanced accounts, and without them the sheet shows it as unavailable. When the module is off, the sheet shows no choice, only a note that names the one type.
A participant's wallet type is fixed at creation. The Console has no control that converts an EOA into a smart account or a single-sig into a multisig. Correcting a wrong choice means creating a new participant, and the old one keeps its own history. This page has no delete or archive control for a participant you created. Only a multisig draft can be deleted, by its creator, before it is finalised.
Troubleshooting
Work as is disabled and I do not understand the reason
The reason names what is missing. “No wallet, so you cannot work as this participant” means the participant has no wallet that can act in this organisation. “No smart wallet, so you cannot work as this participant” means an organisation participant has no smart wallet yet, in an organisation that uses advanced accounts. “Holds 2 signing keys. Revoke all but one, or use lost-wallet recovery, to act as this participant” means the participant signs directly and holds more than one live key, so none of them is the address that can act for it. On your own participants in the You card, the reason can instead say why their wallet cannot sign here, for example “This organisation can sign for too few of this smart wallet's signers to reach its threshold.”
A participant I manage has no identity contract
Identity provisioning is a separate step that runs right after a participant is created. A transient failure can leave the participant record without an identity contract. Open that participant's identity tab, which explains the gap and offers Create identity to provision the missing identity.
I cannot add signers to a multisig draft
If the “First signer wallet” picker shows “None of your wallets can sign in this organisation” and does not let you continue, you have no EOA or single-sig participant of your own in this organisation. Create one first, then start the multisig again. It becomes the first signer.
If you already have signers seated but Create multisig · N of M stays disabled, an invite is still pending. It resolves when the person you invited opens the invite link and joins, or when you revoke it. An invite link expires after seven days. An expired invite reads “Expired”, no longer blocks “Create multisig · N of M”, and leaves its seat empty.
For an expired invitation, clear the row with its remove button and send a new invite. For a lost link on a pending invite, 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.
A participant I expect to see is missing from the table
This table lists only the participants you hold a way into, not every participant that exists. Ask the participant's owner to seat you as a signer on its wallet, or an organisation owner to give you the role that reaches it. 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?
Only a multisig draft. Its creator can delete it before finalising, and nothing of it remains. A deployed multisig and every other participant you created stay, and this page has no control that removes them. An identity manager can remove a registration with “Remove registration”, as On-chain identity describes.
A button is disabled and says the role sits on another participant
The role for the action sits on a wallet that belongs to a participant you can work as, so the button is disabled while you work as someone else. Point at or select the button. The reason names that participant and offers Work as followed by its name. Select it and the Console switches to that participant on the same page. When the participant is a multisig wallet, the reason also gives its signing threshold, and the action you take there waits for the other signers. When you cannot work as the participant, the reason says the participant is not available for actions, and when no participant of yours owns the wallet, it names only the wallet address.
Frequently asked questions
Can I work as two participants at the same time?
Not from Console browser tabs, since they all share one active participant for the session. Working as two at once needs the Platform API, where each request names its participant in the X-Participant header and concurrent requests can name different ones. Delegated Authority explains how a request names its participant.
What happens if my access to the active participant is revoked while I am using it?
The platform checks your access on every request, so a revocation takes effect on the first request after the platform sees the change. A screen that only reads data then loads for your default participant, which is you unless you made another participant your default, and the Console moves to it. A notice titled “You can no longer work as” followed by the participant's name tells you that you lost access, and reads “You can no longer work as this participant” when the Console has no name for it. An action that changes data for the participant you lost access to does not run. A dialog with the same “You can no longer work as” title says “You lost access to this participant, so the action did not run and nothing was sent.” and offers Continue as yourself. Select it. Before you run the action again, check that it should still run for the participant the account menu now names. The platform records the refusal in the audit trail. Through the API, a read that names a participant you lost answers in your own context with an X-Participant-Dropped response header, and a write returns DALP-0524.
Does creating a participant make it the one I work as?
No. Creating a participant adds it to your list. To work as it, select Work as on its row once it is ready.
What do the Type and Your role columns show?
The “Type” column reads one of three values:
- Person: your own participant, a participant you create with “Create participant”, or a person you work as through a wallet you sign for.
- Multisig wallet: a deployed multisig, which never shows “Person”. The same label appears on its page under “Shared accounts”.
- Organisation: the active organisation's own record.
The “Your role” column reads one of four values:
- Owner: a “Person” row your account holds, including your own participant.
- Signer: a “Person” row you reach through a wallet you sign for, and every “Multisig wallet” row.
- Identity manager: only the “Organisation” row.
- Admin: only the “Organisation” row.
Why does the Organisation row show Identity manager instead of Admin?
The list shows the “Organisation” row when you hold the organisation's identity manager role, its administrator role, or both. With both, Your role reads “Identity manager”. With the administrator role alone, it reads “Admin”. For what each role lets an operator do, see Delegated Authority.
Do I need to finish setting up a multisig participant in one sitting?
No. An open draft keeps its state, and Resume in the “Multisig drafts” section of “My participants” reopens it in a later session. Nothing deploys until you finalise. A stale draft can need a revoke and a new invite before “Create multisig · N of M” is available.