> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-0-2/documentation/user-management/access-permissions-for-admin-ui.md).

# Access Permissions for Admin-UI

The permission system of Connectware enables a fine-grained assignment of permissions per roles and users. In particular, if some users should be able to access only a limited set of features on the Admin-UI, it is possible to choose the particular features to see (*read* access) or to configure (*write* access).

* Users with the default administrative role `connectware-admin` have *read* and *write* access to *any operation* within Connectware.
* Users with the default role `minimum-access` can log into the Admin-UI and have limited access to the application. The features can be found at:

{% content-ref url="/pages/4Kh6mdCsPqHhpqHuBx00" %}
[Minimum Access Role Pages](/2-0-2/documentation/user-management/access-permissions-for-admin-ui/minimum-access-role-pages.md)
{% endcontent-ref %}

It is always possible to grant additional *read* or *write* permissions to users and roles. To achieve this, the respective HTTP and MQTT paths need to be assigned to some roles, then assigning those roles to the users that should be allowed to access this information. The section below lists the various Admin-UI pages and operations, and shows which HTTP and MQTT permissions must be available so that users will be able to perform the listed operation.

{% content-ref url="/pages/yVDOIqhVZmcKjtLbKFxt" %}
[UI Access](/2-0-2/documentation/user-management/access-permissions-for-admin-ui/ui-access.md)
{% endcontent-ref %}


---

# 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.cybus.io/2-0-2/documentation/user-management/access-permissions-for-admin-ui.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.