> For the complete documentation index, see [llms.txt](https://docs.zata.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zata.ai/subusers/roles.md).

# Roles

A role defines the permissions assigned to a user in the Zata.ai environment. It controls what actions a user is allowed to perform, such as reading data, writing data, or managing system configurations.

Roles help in maintaining security and proper access control by ensuring that each user has only the permissions required for their responsibilities.

Common roles include:

* **Read:**\
  Allows the user to view and download data. No changes can be made.
* **Write:**\
  Allows the user to upload and modify data but does not allow deletion or management of system settings.
* **Read and Write:**\
  Allows the user to both view and modify data.
* **Full Access:**\
  Provides complete control over the account, including managing users, buckets, policies, and settings.

steps to create a subuser and assign a role: [subuser](https://docs.zata.ai/user/create-a-subuser) 


---

# 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.zata.ai/subusers/roles.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.