> For the complete documentation index, see [llms.txt](https://docs.bloxchain.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxchain.app/platform-guide/operate/my-access.md).

# My access

Check which roles your connected wallet holds on this account and which steps of which actions it may perform.

**Where:** Account rail footer → **My access**, or the ⋯ menu → **My access**

<figure><img src="https://2633730519-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GcVTQuj6X0G3RZ3YY7r%2Fuploads%2Fgit-blob-637fe9045b2b05b9b363676f56f32bd6f4a2440e%2F27-my-access.png?alt=media" alt="My access page showing Your roles with OWNER_ROLE, open requests from you, and a What you can do card listing operations under Request and Approval" width="1000"><figcaption><p>Your roles (1) is what the account grants this wallet. What you can do (2) turns that into the steps you may actually take. Execute is absent here because submitting a signed payload is the broadcaster's right, not the owner's.</p></figcaption></figure>

## Your roles

The **YOUR ROLES** card shows your connected address and one chip per role it holds, protected roles and custom roles alike. Each chip prints the role name as it is stored on-chain, so the protected roles read **OWNER\_ROLE**, **BROADCASTER\_ROLE** and **RECOVERY\_ROLE**. A wallet can hold several roles at once.

Below it, "N open request(s) from you" counts requests you started that are still in [Approvals](/platform-guide/operate/approvals.md).

The rail footer shows a compact version at all times, for example "Owner · 1 role · Request". When no wallet is connected it reads "Connect wallet to view".

## What you can do

The **What you can do** card lists "Operations you can act on at each phase." Chips are grouped under the three phases:

| Phase        | You may                                      |
| ------------ | -------------------------------------------- |
| **Request**  | Start these actions from New request         |
| **Approval** | Approve or cancel these actions in Approvals |
| **Execute**  | Submit signed transactions for these actions |

Filter by execution path with **All** · **Delayed** · **Signed** · **One sign** to see, for example, which actions you can start with **Sign** rather than **Wallet**.

An action appears here only when three things line up for your role: a permission at that step, a granted gate, and (where relevant) a configured allowlist. If an action is missing that you believe you should have, one of those three is not set.

## Empty state

"This wallet is not assigned to any role yet. An admin can add you under Signers." with a **Go to signers** link.

What to ask the admin for, in order:

1. Add your address as a signer with the right role ([Signers](/platform-guide/access/signers.md)).
2. Make sure that role is assigned at the step you need ([Manage permissions](/platform-guide/policies/manage-permissions.md)).
3. Make sure the role's gate is granted ([Gates](/platform-guide/policies/gates.md)).

## How this relates to Signers and Roles

My access is the read-only, self-centred view of the same on-chain data that admins edit on [Signers](/platform-guide/access/signers.md) and [Roles](/platform-guide/access/roles.md). Signers answers "which addresses hold which roles"; Roles answers "what can each role do"; My access answers "what can I do right now with this wallet". Switching wallets changes the page immediately.

## Related

* [Signers](/platform-guide/access/signers.md)
* [Roles](/platform-guide/access/roles.md)
* [New request](/platform-guide/operate/new-request.md)
* [Help](/platform-guide/help.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bloxchain.app/platform-guide/operate/my-access.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.