> For the complete documentation index, see [llms.txt](https://docs.umh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umh.app/management-console/users-and-permissions/roles-reference.md).

# Roles Reference

Roles are not the same in every account. Work out which setup you have in [Users and Permissions](/management-console/users-and-permissions.md) first, then read the matching section below. There is deliberately no combined table.

## Roles per location

Three roles apply at the locations a user or instance is assigned to.

| Role          | What it allows                                                                                                                                                                            |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Account Owner | Everything Admin allows, and is able to create, update and delete instances.                                                                                                              |
| Admin         | Everything Editor allows, plus inviting users at the locations where they are an admin. See [Managing users](/management-console/users-and-permissions/managing-access.md#managing-users) |
| Editor        | Create and modify resources, such as bridges and data models. Cannot manage users or instances.                                                                                           |
| Viewer        | Read-only. See resources and their state, change nothing                                                                                                                                  |

In addition to setting roles, user access is set on a per-location basis, at the granting person's desired location granularity. Exceptions set at a lower location override what is inherited, see [Permission inheritance](/management-console/users-and-permissions/location-based-permissions.md#permission-inheritance).

These capabilities apply in the Management Console. They do not apply on an `umh-core` instance, which does not check the role behind a request, see [What roles do not cover](/management-console/users-and-permissions.md#what-roles-do-not-cover). The Management Console ensures that a user is allowed to talk to an instance instead.

## One role for the whole company

Here your role is not tied to a location. **Current Role** on the **Permissions** tab names it, and the permission matrix underneath shows which groups of actions it covers:

| Permission group | Covers                                                |
| ---------------- | ----------------------------------------------------- |
| Get actions      | Read-only operations for viewing resources and states |
| Edit actions     | Operations that modify existing resources             |
| Delete actions   | Operations that remove resources                      |
| Deploy actions   | Operations for deploying new resources                |
| Test actions     | Operations for testing configurations                 |
| System actions   | System-level operations                               |
| Company actions  | Company-level operations                              |

Expand a group in the matrix to see the individual actions in it. The matrix is generated from the role you hold, so it is the list for your own account rather than a general one. Like the roles above, it covers the console only, see [What roles do not cover](/management-console/users-and-permissions.md#what-roles-do-not-cover).


---

# 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.umh.app/management-console/users-and-permissions/roles-reference.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.