> 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/location-based-permissions.md).

# Location-Based Permissions

## Locations

A location is a position in your company's tree. Level 0, the enterprise, is the only level you have to use. Everything below it is yours to choose, whether you follow ISA-95, KKS, or your own naming.

Location paths use the same dot-separated format as [topic paths](/usage/unified-namespace/topic-convention.md):

* `ACME` (enterprise)
* `ACME.Munich` (enterprise, site)
* `ACME.Munich.Assembly` (enterprise, site, area)
* `ACME.Munich.Assembly.Line1` (enterprise, site, area, line)
* `ACME.Munich.Assembly.Line1.Cell5` (enterprise, site, area, line, work cell)

Add more levels if your organization needs them.

## Roles

The full capability list is in the [Roles Reference](/management-console/users-and-permissions/roles-reference.md).

A user can hold different roles at different locations, for example Admin at `ACME.Munich.Assembly.Line1` and Viewer at `ACME.Munich.Assembly.Line2`.

### Permission inheritance

Permissions inherit downward. Access at `ACME.Munich` also grants access to everything under Munich, including `ACME.Munich.Assembly.Line1.Cell5`.

You can override an inherited permission for a specific location. A user can be a Viewer at `ACME.Munich.Assembly` and an Admin at `ACME.Munich.Assembly.Line1.Cell5` only.


---

# 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/location-based-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.