> 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/1-11-0/documentation/user-management.md).
# User Management
Controlling Connectware access through secure identity management and permissions.
User management in Connectware allows you to control access to your systems through well-defined identities and permissions. This chapter explains how to manage users, roles, and permissions.
{% hint style="info" %}
Managing users and roles requires admin role privileges or corresponding permissions.
{% endhint %}
## Users, Roles, and Permissions
The main concept of managing access in Connectware is done via users, roles, and permissions:
* **Users**: A known identity (person or software/hardware agent) with associated data permissions and/or administrative access. See [Users](/1-11-0/documentation/user-management/users.md).
* **Roles**: A group of permissions that can be assigned to multiple users. See [Roles](/1-11-0/documentation/user-management/roles.md).
* **Permissions**: Specific access rights to resources (via MQTT topics or HTTP endpoints). See [Permissions](/1-11-0/documentation/user-management/permissions.md).
Example of users, roles, and permissions
## Hardware Devices
For hardware devices connecting to Connectware, we recommend using the [Client Registry](/1-11-0/documentation/client-registry.md). Instead of manually creating user accounts through the Admin UI, the Client Registry enables:
* **Self-registration**: Devices can self-register using either MQTT or REST API approaches.
* **Secure credential handling**: Eliminates risks associated with manual password sharing.
* **Certificate support**: Advanced registration with certificate signing requests (CSR) for enhanced security.
* **Controlled approval**: Administrator review of all registration requests before granting access.
* **Granular permission management**: Newly registered devices have no permissions by default, allowing precise control over device capabilities.
---
# 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/1-11-0/documentation/user-management.md?ask=&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.
