# Participant access

Source: https://docs.settlemint.com/docs/console/asset-lifecycle/venues/participant-access
See everything that decides whether one wallet can trade on a venue, and change the broker and the access on a private instrument.

The **Participant access** page shows why one wallet can or cannot trade on a venue. It gathers the venue's admission policy, a block, the verifications the wallet's identity holds, freezes on the listed securities, private-instrument participant lists, the access profile of each instrument, and desk limits. Instrument status, the trading calendar and the token's compliance rules can still refuse an order and are not on this page.

## Before you start [#before-you-start]

- **The Venue operator or Venue admin role.** Only a holder of the venue operator or venue admin role on this venue can open the page. Anyone else gets a not-found answer.
- **The Platform admin or Owner role, to change access on a private instrument.** Saving a participant's access on a private instrument needs it.
- **A wallet to look at.** The page opens for one wallet address under the venue. A wallet counts as a participant of the venue when it is a venue member, appears on an instrument's participant list, or has an active block.

## Steps [#steps]

### Open the page for a wallet [#open-the-page-for-a-wallet]

Open it from the **View venue access** link under a wallet's address in a private instrument's participant list, or from the "Holders" tab of an asset. In the holders table, the row menu of a holder shows "View access on" and the venue's name for each venue that lists the asset as an instrument's security. The page opens under the venue, with the wallet's address in the breadcrumb.

### Read the sections [#read-the-sections]

| Section | What it shows | Where you change it |
| --- | --- | --- |
| Admission | The wallet's registered identity, whether the venue admits it, whether it is a venue member, whether the venue requires membership, the venue's visibility, and the account status with any restrictions on trading, securities transfers or withdrawals | **Edit admission** opens the venue's **Permissions** tab |
| Block | Whether the venue blocks the wallet, since when, and the reason | **Manage blocks** opens the **Permissions** tab |
| Required verifications | Each verification topic the venue requires, marked **Held** or **Missing** for the wallet's identity | **Edit requirements** opens the **Permissions** tab |
| Freezes | For each security listed on the venue, whether the wallet's address is frozen and how much of its balance is frozen, in the security's own units | The security's name opens its **Holders** tab |
| Private instrument memberships | The private instruments whose participant list includes the wallet, with the wallet's classification and the time it was added | The instrument's name opens the instrument, where you edit its participants |
| Access per instrument | For every instrument of the venue, the wallet's access profile and what remains after overrides: placing orders, the watchlist, order book depth, instrument groups, and whether the instrument denies the wallet | **Edit access** opens the participant access editor for a private instrument the wallet belongs to |
| Desk limits | The approved desk limits for the wallet, the instrument each applies to or all instruments for an older venue-wide limit, and the approval time | **Manage desk limits** opens **Desk administration** |

**Admitted** applies the same admission rule as order intake. A discoverable venue that requires no verification topics and no membership admits any wallet. Every other venue admits a wallet only when it has a registered identity that holds every required verification topic and, if the venue requires membership, is a venue member. When "Admitted" reads No, "Reason not admitted" says whether the wallet has no registered identity or its identity does not meet the admission requirements. The block is shown apart in its own section. A limit that is proposed and not approved does not appear under "Desk limits", because it constrains no order.

## Assign a trading member [#assign-a-trading-member]

To assign a broker, open the wallet's "Participant access" page. Its "Trading member" section names the participant, its broker and the trading member of its orders. Select **Assign broker** or "Change broker", search for the broker participant, enter a reason and confirm with your wallet. "Remove broker" makes the participant its own trading member again. A venue operator or venue admin makes the change, and it waits for a second person only while the "Administration" row under "Approvals" on [General](https://docs.settlemint.com/docs/console/organisation-settings/general#approvals) protects the "Venue administration" group. The reason goes into the audit log with the broker before and after. The change applies to orders placed from that moment on. Earlier orders keep their trading member, as [Orders](https://docs.settlemint.com/docs/console/asset-lifecycle/venues/orders#read-an-orders-trading-member) describes.

## Edit a participant's access on a private instrument [#edit-a-participants-access-on-a-private-instrument]

On a private instrument's participant list, **Edit access** opens the participant's access on that instrument. The editor holds these settings:

- **Access profile**: "Full access", "Watchlist only", or a profile the venue named.
- **Place orders**: "Follow profile", shown with the profile's value in brackets, or "Allow" or "Block".
- **See the instrument in watchlists**: "Follow profile", or "Allow" or "Block".
- **See order book depth**: "Follow profile", or "Allow" or "Block".
- **Instrument groups**: follows the profile, or "Only the groups I choose" with at least one group, or "All instrument groups".

Enter a "Reason for the change", select **Save access** and verify your wallet.

Saving replaces the whole access, so a setting you leave on "Follow profile" drops any earlier override.

Only a platform administrator or the organisation owner can save. A wallet barred from the instrument shows every setting off until the bar is lifted. An order on an instrument whose group the wallet may not trade is refused with "This account may not trade the instrument group of this instrument."

## You should see [#you-should-see]

- Reopen the page for the wallet and check that the section you changed now reads as intended.
- **Admitted** reads Yes only when the wallet passes the venue's admission rules, and "Access per instrument" shows what remains after the access profile and any overrides.

## Troubleshooting [#troubleshooting]

**The page says the wallet is not a participant**

A wallet counts as a participant of the venue when it is a venue member, appears on an instrument's participant list,
or has an active block. For any other wallet the page reads "This wallet is not a participant of this venue" and
offers **Open permissions**, the tab where the wallet is admitted.

**The page says not found**

Opening the page needs the Venue operator or Venue admin role on this venue. Ask a venue admin to grant it on
[Permissions](https://docs.settlemint.com/docs/console/asset-lifecycle/venues/permissions).

## API routes [#api-routes]

| Task | Route |
| --- | --- |
| Read one wallet's access to the venue | `GET /api/v2/addons/trading-venues/{venueAddress}/participants/{walletAddress}/access` |
| Read or replace access on a private instrument | `GET /api/v2/addons/trading-venues/{venueAddress}/markets/{marketId}/participants/{walletAddress}/access` and `PUT /api/v2/addons/trading-venues/{venueAddress}/markets/{marketId}/participants/{walletAddress}/access` |

The first route answers a non-participant with a 404 and the code `TRADING_VENUE_PARTICIPANT_NOT_FOUND`. The request and response fields are in the [v2 API reference](https://docs.settlemint.com/docs/api-reference/v2).