> 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/administration/admin-users.md).

# Security

## Overview

The ServoyCloud Users section allows you to manage users in a namespace. Here, you can find important user information and perform user-related actions. You can change lock status, access user roles and manage permissions.

## User overview

The User Overview provides a list of users in the namespace, along with their details:

**Gravatar:** The user gravatar image. See [My Profile](/reference/servoy-cloud/cloud-control-center/home/user-profile/my-profile.md) on how to set this up.

**Username:** The email address associated with the user account.

**Assigned Role:** The user's current role.

**Last Login Date:** The date of the user's last login to ServoyCloud.

**Lock Status:** Indicates the user lock status, whether the user is **"Locked"** or **"Unlocked"**.

#### **Manage user menu** ![](/files/Z3hnZFHMXrgYHNkGkatj)

To manage a user, click the button located at the end of the user information entry. This menu offers various actions related to the user.

### Lock/Unlock user

Locking a user prevents them from logging into ServoyCloud, while unlocking allows access. To lock or unlock user, follow these steps:

1. Go to the user overview.
2. Click the ![](/files/Z3hnZFHMXrgYHNkGkatj) manage user menu for the user you want to access
3. Choose **"Change Lock Status"**
4. Toggle the switch to lock or unlock.
5. Save to apply the changes.

### Add user

To add or invite users to a ServoyCloud namespace, follow these steps:

1. In the main Security Users view, click the **"Add User"** button.
2. Provide the user details.
3. Send the invitation.

The user will receive an email to confirm their ServoyCloud account. To confirm the account:

1. Click the **"Confirm"** button in the email.
2. Follow the prompts to create a password by resetting the system-given one.

### Delete user

You cannot directly delete or remove a user from a namespace in ServoyCloud. However, you have alternative options:

1. **Lock User**: If you wish to prevent a user from logging into ServoyCloud, you can achieve this by changing their lock status to locked from the manage user menu ![](/files/Z3hnZFHMXrgYHNkGkatj) in the user overview.\\
2. **Assign a different role**: If your goal is to limit a user's access to specific ServoyCloud features, consider assigning them a different role. Note: When users are initially invited or added to the namespace, they are assigned the role [Observer](/reference/servoy-cloud/cloud-control-center/administration/admin-users/cloud-roles.md#observer). See [ServoyCloud Roles](/reference/servoy-cloud/cloud-control-center/administration/admin-users/cloud-roles.md) for more details.

By following these approaches, you can effectively manage ServoyCloud Users, ensuring the appropriate level of access and security for your namespace.

\
\\

\
\
\
\\

## Overview


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.servoy.com/reference/servoy-cloud/cloud-control-center/administration/admin-users.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.