> For the complete documentation index, see [llms.txt](https://docs.servoy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.servoy.com/reference/servoy-cloud/cloud-control-center/user-management.md).

# User Management

Page reference for User Management of ServoyCloud Applications

## Overview

The **User Management** feature in Servoy Cloud allows you to manage who can access your Servoy Cloud Applications and what they are allowed to do. It is split into two key areas:

1. **Users:** Add and manage user accounts, including their details, status, and the roles assigned to them.
2. **Roles:** Create and manage roles, which are groups of permissions that define what actions users can perform.

{% hint style="info" %}
To fully configure access and permissions, you will need to set up [application permissions](/reference/servoy-cloud/cloud-control-center/application-overview/applications/security.md#create-permission), which control what each role is allowed to do within the application.
{% endhint %}

The following sections provide detailed instructions on managing users and roles.


---

# 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.servoy.com/reference/servoy-cloud/cloud-control-center/user-management.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.