> For the complete documentation index, see [llms.txt](https://cleyrop.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cleyrop.gitbook.io/docs/documentation-fr-en/administration/gerer-les-utilisateurs-et-groupes.md).

# Manage users

The **Platform Managers** are responsible for account, group, and role management on the platform.

## Available profiles

Each user belongs to one of Cleyrop's three profiles:

<table><thead><tr><th width="374">Profile</th><th>Main access</th></tr></thead><tbody><tr><td><strong>Viewer</strong></td><td>View-only access to project assistants.</td></tr><tr><td><strong>Data Worker</strong></td><td>+ Full access to the Data &#x26; AI, The Factory and DevSpace project features</td></tr><tr><td><strong>Platform Manager</strong></td><td>+ Access to the administration console and data source management</td></tr></tbody></table>

## User statuses

A user can have two statuses:

* **Activated** : full access to the platform.
* **Deactivated** : access is suspended, but data and projects are retained.

**When deactivating:**

* the user loses access to all services,
* their DevSpace is stopped,
* they will be able to find their items again upon reactivation.

When deactivating, two options are offered regarding asset ownership (projects, datasets, dataflows, apps):

* **Reassign ownerships** *(default option, recommended for permanent deactivations)* : all assets are transferred to the project manager.
* **Keep ownerships** : the assets remain assigned to the deactivated account. The user will automatically find them again upon reactivation.

<figure><img src="/files/ba86f82e4e9718c16b0c35b87c38443e98c43a97" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="warning" %}
By keeping ownerships, the assets will remain assigned to an inactive account. Make sure that critical assets remain accessible and manageable during the deactivation period.
{% endhint %}

**When deleting:**

* the user loses access to all services,
* its responsibilities (projects, datasets, dataflows, apps) must be **reassigned**,
* their DevSpace is deleted,
* their Studio is deleted (as well as all assets it contained).

## User management

Platform Managers can:

* **Create a user** via the “Administration → Users → Create” panel:
  * You can directly add them to a project or group upon creation
  * Depending on your environment configuration, you can enable or disable **MFA** for the user
* **Modify** the information and profiles at any time (e.g. switch from Viewer to Data Worker).
* **Reset** a password (a new temporary password is generated).
* **Export** the user list in CSV format for audit or internal tracking.

{% hint style="warning" %}
When changing a role to a more restricted profile (e.g. Platform Manager → Viewer), ownership of the relevant projects or datasets must be transferred.
{% endhint %}

## Managing allowed IPs

The goal is to allow **Platform Managers** to manage allowed IP addresses directly from the Cleyrop platform.

From the *User → IP Whitelist,* you can:

* **allow IPs** or CIDR blocks,
* **view** the existing allowed IPs,
* **delete** an allowed IP.

### Add one or more IPs

{% hint style="info" %}
Supported format: **IPv4** and **CIDR**

To quickly retrieve their public IP, users can use a dedicated service (e.g. <https://whatismyipaddress.com/>) and send you the IPv4 value
{% endhint %}

From the *User → IP Whitelist,* click Create, then:

* fill in a **description field** (e.g. “ACME Client — office network”)
* enter **one or more IP/CIDR**, separated by commas\
  Example: `192.168.0.1, 10.0.0.0/24, 8.8.8.8`
* validate

{% hint style="warning" %}
If you enter multiple values at once, under the same description, they will form a **single block** and can only be managed / deleted together.
{% endhint %}

### List and manage IPs

Once created, you can view and search the list of allowed IPs.

Each row displays:

* the description
* the CIDR block(s)

A CIDR block (for *Classless Inter-Domain Routing*) is a way to represent an IP address + the size of the network it belongs to. Example:

* `192.168.1.42/32` ⇒ **just this IP**
* `192.168.1.0/24` ⇒ covers **all IPs from 192.168.1.0 to 192.168.1.255**

You can click delete <i class="fa-circle-trash">:circle-trash:</i> to remove an entry.

#### Non-editable values

Some values are **not editable or deletable**, including:

* IPs required for **Cleyrop internal deployment**,
* IPs already whitelisted before this feature was introduced.

These entries appear in the list but cannot be modified.

## Customize the platform logo

The **Visual identity** tab lets you replace the Cleyrop logo with your organization's logo. The change is applied immediately for all users.

1. Go to **Administration > Users**.
2. Click the **Visual identity**.
3. In the section **Logo**, upload your file or click on **Upload**.

{% hint style="info" %}
Prefer a horizontal PNG or SVG file (\~240×60 px) with a transparent background.
{% endhint %}

<figure><img src="/files/c71d8b922f7db41bd625f423197fa588cc4c9b8d" alt=""><figcaption></figcaption></figure>
