> For the complete documentation index, see [llms.txt](https://docs.oveka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oveka.io/administration/user-and-group-management/user-roles.md).

# User Roles

Learn how Oveka uses roles to control access and management features.

### Overview <a href="#overview" id="overview"></a>

Oveka has a few different roles that can be used to control what users can access and manage.&#x20;

| Role               | What they can do                                                                                                                                                      |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Account Owner      | Can manage billing settings for the tenant. This role is automatically assigned to the user who created the organisation.                                             |
| Team Administrator | Can view/manage all settings within their organisation, add additional users/groups, and create additional organisations.                                             |
| Team Member        | Can use the Oveka portal to manage personal data integrations within their DataBridge bundle and download the PromptGuard browser extensions and native applications. |

<br>


---

# 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.oveka.io/administration/user-and-group-management/user-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.