> 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/developers/rbac-best-practices.md).

# RBAC best practices

Operational guidance for designing roles and permissions on production Accounts.

## Principle: least privilege

Grant the **minimum** actions each role needs per operation. A payroll requester should have **request** on transfer ops — not **approve**, **execute**, or admin schemas.

## Separate duties

| Function             | Suggested split                      |
| -------------------- | ------------------------------------ |
| Day-to-day transfers | Requester + Approver roles           |
| Policy changes       | Admin role + timelock + Owner path   |
| Meta-tx broadcast    | Dedicated Broadcaster wallet(s)      |
| Emergency            | Recovery on hardware-isolated wallet |

## Protected vs custom roles

Never treat **Owner**, **Broadcaster**, or **Recovery** as day-to-day operator roles. Configure them once under [Security settings](/platform-bloxchain.app/overview-1/security-settings.md).

## Naming and documentation

* Use clear role names (`Treasury Approver L2`, not `Role7`)
* Maintain an off-chain matrix mapping roles → people → operations (your SOC process)
* Mirror changes in [Permissions](/platform-bloxchain.app/overview-1/permissions.md)

## Non-revocable grants

Some admin schemas use **non-revocable** grants by design. Review before assigning to custom roles — see [Runtime RBAC](/protocol/runtime-rbac.md).

## Testing

* Rehearse on Sepolia before mainnet
* Use [My access](/platform-bloxchain.app/overview/my-access.md) with each test wallet
* Complete [Production readiness](/developers/production-readiness.md)

## Reference

Imported detail: [Runtime RBAC](/protocol/runtime-rbac.md) · [Best practices (protocol)](/protocol/best-practices.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/developers/rbac-best-practices.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.