> 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/roles-and-members.md).

# Roles & members

**Audience:** Admin · **App path:** Deployment → **Roles** / **Members**

Create **custom RBAC roles** and assign wallets. **Owner**, **Broadcaster**, and **Recovery** are protected roles — assign them under [Security settings](/platform-bloxchain.app/overview-1/security-settings.md), not here.

## Create a role

**Deployment → Roles** → **Add role**

| Field           | What to enter                                                                          |
| --------------- | -------------------------------------------------------------------------------------- |
| **Role name**   | Unique label (e.g. `Treasury Requester`) — do not reuse Owner / Broadcaster / Recovery |
| **Max wallets** | Cap on members (default `10`)                                                          |

**Sign** → **Execute** the role-config batch.

Recommended names per use case: [Treasury](/platform-bloxchain.app/use-cases/treasury.md#step-3--create-roles) · [Vault](/platform-bloxchain.app/use-cases/vault.md#step-3--create-roles).

## Assign members (draft → commit)

Membership edits use a **draft** pattern — changes are not on-chain until you sign and execute a role-config batch.

### By role — Deployment → Roles

1. Open a **custom role** (not a protected Security role).
2. Open the **Members** tab → **Edit**.
3. Add or remove wallet addresses (checkboxes). Protected roles show members as read-only — edit those in **Security**.
4. Review **Pending changes** (added / removed wallets).
5. **Reset** — discard the draft, or **Continue** — open the submit drawer.
6. **Sign** in your wallet → **Execute** the role-config batch.

### By wallet — Deployment → Members

1. Select a wallet from the access registry.
2. Open the **Roles** tab → **Edit**.
3. Check or uncheck **custom roles** for that wallet (system roles are read-only here).
4. Review **Pending changes** → **Reset** or **Continue**.
5. **Sign** → **Execute** the batch.

> Same commit bar on both paths: pending diff summary, change count badge, **Reset**, and **Continue** before the on-chain batch.

## After assignment

1. Set [Permissions](/platform-bloxchain.app/overview-1/permissions.md) per operation.
2. Connect each test wallet → verify [My access](/platform-bloxchain.app/overview/my-access.md).
3. [Submit a request](/platform-bloxchain.app/overview/submit-request.md) with permitted wallets only.

## Verify

* Each wallet shows expected roles in **My access**.
* Unauthorized wallets cannot submit.

## Next steps

* [Connect your application](/platform-bloxchain.app/overview-1/connect-your-application.md)
* [Configure overview](/platform-bloxchain.app/overview-1.md) · [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/roles-and-members.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.