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

# Roles and permissions

Roles define what users can access and manage within your organization. Each role comes with different permissions, from managing the entire organization to accessing specific teams and features.

### Owner&#x20;

Has full access to the organization and can manage company-wide settings, users, teams, models, apps, billing, and other organization-level configurations.

### Team Owner

Manages their assigned team and the users within it. Team Owners can choose which models are available to their team, overriding the company-wide model settings for that team. Apps remain managed at the company level.

### User&#x20;

Has access to the models, apps, and other resources made available to them through their organization and team. Users cannot manage organization- or team-level settings.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nexos.ai/workspace/settings/organization/roles-and-permissions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
