> For the complete documentation index, see [llms.txt](https://docs.brahma.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brahma.fi/brahma-accounts/brahma-pro/team-management-and-access-control/inviting-operator-and-role-management.md).

# Inviting Operator & Role Management

#### Here’s a deep dive into the difference between owner vs operator

To invite an operator, admins can directly add their operator address to extend access to your account. Joining **operators will only be able to view Sub-Accounts assigned to them** and will not be able to make any global-level changes to the main account.

Only your account Admins can set upper limits on Sub-Account transactions and pre-fund the Sub-Account before transferring it to any operators for specific actions and automations, making operations ready to execute as soon as control is exercised.

Role-based policies enable users to tailor access control to automation-specific needs, ensuring that only authorised operators can interact with your assets and execute transactions.

**Here’s a deep dive into the difference between owner vs operator access:**

To make changes to set-up policies, users can select specific rules they wish to edit and proceed to customise. This step requires a signature to confirm the changes and can only be accessed by Admins.

***

*Note: You can also add various addresses and tag them by names/use cases and directly access them via the account’s Address Book. The Address book extends the functionality of additional security and error handling during send transactions with your account. Furthermore, it makes recurring transactions convenient and traceable within the historical view.*


---

# 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.brahma.fi/brahma-accounts/brahma-pro/team-management-and-access-control/inviting-operator-and-role-management.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.