> 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-bloxchain.app/overview-1/permissions.md).

# Permissions

**Audience:** Admin · **Time:** \~15 min

Grant which **workflow steps** each role may perform per registered operation.

## Where to edit

| Path                                                            | When                                          |
| --------------------------------------------------------------- | --------------------------------------------- |
| **Deployment → Operations** → select operation → **Access** tab | Default — per-operation permission editor     |
| **Help & setup** → **Policy by operation**                      | Jump list across all operations (same editor) |

## Steps

1. Open an operation (e.g. **Native Transfer**) → **Access**.
2. For each **custom role**, toggle the steps that role may perform.
3. Use app labels (match [Operations](/platform-bloxchain.app/overview-1/operations.md) registration):

| App label                     | Typical grant                                 |
| ----------------------------- | --------------------------------------------- |
| **Pending Request**           | Requester role only                           |
| **Sign and approve request**  | Approver role                                 |
| **Finalize approved request** | Approver or **Broadcaster** (meta-tx execute) |
| **Cancel**                    | Optional — compliance / admin                 |

4. Apply [separation of duties](/introduction/operational-model.md) — avoid request + approve on one production wallet.
5. **Sign** → **Execute** role-config changes when prompted.

![Policy enforcement](/files/9IK0oZUnjnq4kEopzSJL)

Use-case matrices: [Treasury](/platform-bloxchain.app/use-cases/treasury.md#step-4--grant-permissions) · [External calls](/platform-bloxchain.app/use-cases/external-calls.md#step-5--grant-permissions).

## Verify it worked

* Requester wallet sees operation under [My access](/platform-bloxchain.app/overview/my-access.md) with request only.
* Approver can act on **Open** queue items; cannot bypass timelock.

## Common issues

* **Same wallet holds Pending Request + Sign and approve request** — violates treasury best practice ([RBAC best practices](/developers/rbac-best-practices.md)).
* **Operation invisible to member** — role not assigned under [Members](/platform-bloxchain.app/overview-1/roles-and-members.md).

## Next steps

* [Allowlists](/platform-bloxchain.app/overview-1/allowlists.md)
* [Protected roles](/resources/glossary.md#protected-roles-secureownable) · [Runtime RBAC](/protocol/runtime-rbac.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bloxchain.app/platform-bloxchain.app/overview-1/permissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.