The Permissions tab decides who may discover and trade on the venue, who runs it, and who is blocked. Roles here apply to this venue only. Admission, venue roles, participant depth and participant blocks each have their own card.
The venue's “Permissions” tab with the cards of the venue roles.
The tab reads “Roles here apply to this venue only.” Each venue role, such as “Venue admin” and “Venue operator”, has an address field, the “Grant role” button and a “Current holders” table. The “Admission” card with “Admission policy” and “Admitted identities” follows further down the tab.
Steps
Set the admission policy
Under “Admission policy”, fill in the fields below, then select Save policy and verify your wallet.
- Required verification topics: decimal topic IDs separated by commas or spaces.
- Require membership: switch it on so that only admitted identities may trade.
- Admitted identities only: switch it on to hide the venue from identities that are not admitted.
While the venue's “Trading venues” row is on, or the “Administration” row protects the “Venue administration” group, the change waits for a different venue admin on Desk administration.
With Admitted identities only on, an order from an identity the venue does not admit is answered “No such instrument on this venue”, the same answer as for an instrument that does not exist. The venue's instruments, public ones included, also stay out of the market list for a caller none of whose wallets the venue admits, and opening one by its address answers that the instrument does not exist. The platform operator and the venue's own operators still see them. With it off, the venue stays visible to everyone and the refusal names the cause: the wallet holds no registered identity the venue admits, or its identity does not meet the admission policy. Participant access shows the result for one wallet.
Admit and revoke identities
The “Admitted identities” list shows each member and the date it was admitted, and you can search it by identity address. Enter up to 100 identity addresses in “Admit identities” and select Admit.
To remove a member, enter the “Reason for the change”, open the row's actions menu and select Revoke. “Revoke” stays disabled until you enter a reason.
Grant a venue role
Only a platform administrator can grant or revoke the venue admin role, and the change needs no second person. The platform submits that write as the organisation's operations signer, which holds the venue's admin authority on chain. To grant or revoke the operator or submitter role, one of your wallets must hold the venue admin role, and the change runs under your own signing wallet. Being the organisation owner does not let you change venue roles.
On the card of the role, enter the “Account address” and select Grant role, then confirm with your wallet verification. To end the role by itself, fill in “Remove access after”, as Can a venue role end by itself? describes.
- Venue admin grants and revokes the operator and submitter roles, and resumes a paused venue.
- Venue operator runs the venue: instruments, fees, price bands, halts, order cancels, bust proposals and pausing the venue. Its holder can also cancel any participant's orders and change an instrument's fees and fee account on the venue contract without a second person.
- Venue submitter submits settlement for the venue, and the platform's settlement accounts hold it. Its holder can also cancel any participant's orders on the venue contract without a second person, so grant it to no other wallet.
The “Current holders” table lists each holder with “Granted” and “Access ends”. To take a role from a holder, open the row's actions menu, select Revoke and confirm with your wallet verification. When you cannot change the role, “Revoke” is disabled and says why. The row leaves the list once the change is on chain. Revoking the Venue submitter role from a settlement account stops that account's settlement until you grant the role back, and the prompt says so.
Grant participant depth
Participant depth lets a wallet see order book levels beyond the best bid and ask. Under “Participant depth entitlement”, enter a valid wallet address and select Grant depth or “Revoke depth”, then confirm with your wallet verification. Granting or revoking participant depth needs the Venue admin or Venue operator role, and waits for a second person while the “Administration” row protects the “Venue administration” group.
Block a participant
Under “Participant venue access”, enter the “Participant wallet”, a non-zero EVM address, and a “Reason” that the audit trail keeps. Select Block participant or “Unblock participant”.
A block opens Disable venue access, which warns that the wallet's resting orders are cancelled, and asks for your wallet verification. Only the action that changes the wallet's current state is on. A venue operator or venue admin blocks a wallet, and the block or the unblock waits for a second person only while the “Administration” row under “Approvals” on General protects the “Freezing” group.
Once it is sent, the form clears and names the wallet with the outcome: “Blocked. This wallet can no longer trade or read market data on the venue.” or “Unblocked. This wallet may trade on the venue again.” A block applies to one wallet address and stops it from trading and from reading market data. Another wallet of the same identity is not blocked unless you block it too. The wallet's holdings and order history stay. Its cancelled orders appear as a batch on Mass cancellations. Participant access shows a wallet's block and everything else that decides its access.
Troubleshooting
Grant role and Revoke are disabled
The buttons stay disabled for a role you cannot change, with a line that names the missing authority. Only a platform administrator can grant or revoke the Venue admin role. Granting or revoking the other roles needs the Venue admin role on the wallet that signs.
Frequently asked questions
Can a venue role end by itself?
Yes. Fill in Remove access after when you grant a role on the Permissions tab, or send validUntil with the role change through the API. The end must fall between one minute and one year from now. The platform submits the revocation at that time, and the role ends when the revocation lands on chain. The audit trail records it with the reason “grant expired”.
The wallet that granted the role signs the revocation if it still holds venue admin. If not, the revocation goes to another venue admin wallet that signs this venue's time-boxed grants. If none is available, the organisation's operations signer, which can take venue admin at any time, takes it for that revocation only and gives it up in the same submission. A venue admin whose own admin role ends at a set time can grant a role only for a period that ends before their own. Granting the same role again replaces the end, and a grant without one is permanent. A queued revoke or permanent grant replaces the earlier end date only when it lands. The role list shows each holder's end under Access ends, or “No end date”. The platform raises an operator alert on the first failed revocation, including one still pending 15 minutes after the end, and keeps retrying. Check that alert before you treat access as ended.
API routes
The tab reads and writes admission and roles through the trading venue routes in the v2 API reference.