# Users
In Efento Cloud, **user permissions** are used to control what actions each user can perform within an Organization. This ensures that users can only access the features and data that the Organization owner or administrators intend them to. By assigning appropriate permission levels, you can protect sensitive data, manage sensors and alarm rules securely, and maintain overall control of the Organization’s settings. Within an Efento Cloud Organization, users can be assigned one of three permission levels: **Administrator**, **Manager**, or **Analyst**.
* The **creator of the Organization** is automatically granted **Administrator** permissions, with full access to all locations and features.
* Additional users can be **invited** to join the Organization. When inviting a user, you can assign their **permission level** and define which **locations** they can access, ensuring data security and controlled access.
The table below provides an overview of the **platform functions available to each permission level**.
| | Administrator | Manager | Analyst |
| ------------------------------------------------------------------ | ------------- | ------- | ------- |
| **Dashboard preview** | **✔** | **✔** | **✔** |
| **Generating reports** | **✔** | **✔** | **✔** |
| **Alarm preview** | **✔** | **✔** | **✔** |
| **Configuration of automatic reports** | **✔** | **✔** | **✘** |
| **Configuration of alarm rules** | **✔** | **✔** | **✘** |
| **Sensors, structures and location maps configuration** | **✔** | **✔** | **✘** |
| **Integrations (Webhooks / Slack)** | **✔** | **✔** | **✘** |
| **Formulas / custom measurement types** | **✔** | **✔** | **✘** |
| **Archiving measurements** | **✔** | **✔** | **✘** |
| **Notification manager** | **✔** | **✔** | **✘** |
| **SIM card manager** | **✔** | **✔** | **✘** |
| **Editing of permissions, adding and removing users / API tokens** | **✔** | **✘** | **✘** |
| **System logs preview** | **✔** | **✘** | **✘** |
| **Organization account management** | **✔** | **✘** | **✘** |
Efento Cloud allows **Administrators** to manage users, including adding new users, modifying permissions, and revoking access within an Organization. To manage users, select the **Settings** icon (gear) in the left-hand menu, then choose **Access**.
## **Adding New Users**
New users can be added via the **invitation system**:
1. Click **Add new user** in the top-left corner of the table
2. Enter the user’s **email address** and assign a **permission level**
3. Choose the **locations** that the user is allowed to access.
The invited user will receive an email invitation to join your Organization. If they do not yet have an Efento Cloud account, they will need to create one first. You can invite multiple users at once and assign different permissions as needed.
{% hint style="warning" %}
**Note:** Administrator permissions provide full control over users, sensors, alarm rules, and Organization settings. Assign these privileges only to trusted individuals.
{% endhint %}
* Invited users appear in the **Awaiting Invitations** tab with a **"Sent"** status, indicating the invitation email has been sent but not yet accepted.
* Once the invitation is accepted, the user moves to the **Users** tab.
* If the invitation is declined, the status changes to **"Refused"**.
### Best practices for assigning Efento Cloud permissions
To maintain the highest security and operational efficiency, it is vital to follow the principle of Least Privilege when assigning roles. This means users should only be granted access to the specific data and features necessary to perform their job. When adding new users and assigning privileges on the platform, remember these two crucial best practices:
* **Avoid assigning Administrator / Manager permissions to all users**. Only assign Administrator or Manager permissions to users who are fully aware of the platform’s comprehensive features, as these roles wield significant control over sensors, data, and system-level configuration. Remember that Administrator rights, in particular, grant full control over users, sensors, alarm rules, and the Organisation’s account, and should therefore be reserved for highly trusted personnel only.
* **Assign the permission only to selected locations**. It is a fundamental best practice to assign a permission level and grant access based on specific locations within the organisation’s structure. This ensures that, for instance, a Manager responsible for a specific warehouse can configure sensors in that location but has no visibility or control over another facility.
## **Editing user's permissions**
The table displays all users with access to your Organization and their assigned **permission levels**.
* To **edit a user's permissions**, click the **pencil icon** on the right side of the table. You can adjust the user’s permission level and specify which locations within the Organization they can access.
* To **revoke a user’s access**, click the **pencil icon** and uncheck all locations assigned to that user. This will remove their access to your Organization, but it will **not** delete their Efento Cloud account. Full account deletion can only be performed by the user themselves (see section *Changing the username, language, and password, and deleting the account*).
## **Exporting Users List**
To export a list of all users in your Organization, click **Export users list** in the upper-left corner of the table. A PDF file will be sent to the email address associated with your Efento Cloud account.
---
# Agent Instructions: 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:
```
GET https://docs.efento.io/efento-cloud/advanced/editor/users.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.