> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/connect-v2.1-en/operacion/usuarios.md).

# User management

Editran Connect incorporates a user management system based on **roles** that determines the functionalities each user can access within the application. This separation by roles ensures a more secure and controlled environment, allowing permissions to be assigned according to each profile's responsibilities.

***

## List of available roles

The following describes the roles available on the platform and the permissions associated with each:

| Role                      | Description                                                         | Main permissions                                                       |
| ------------------------- | ------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| **Global administrator**  | User with full control over the platform.                           | Create/edit/delete users, full access to all modules and settings.     |
| **Local administrator**   | User with limited access to specific settings.                      | Management of schedules and report recipients (if allowed by license). |
| **Operational user**      | User intended for monitoring and executing tasks.                   | Access to channel viewing, execution of broadcasts.                    |
| **Signer**                | User authorized to sign documents (requires signature module).      | Access to own certificates, management of digital signatures.          |
| **Signing administrator** | User with the ability to manage parameters of the signature module. | Management of file groups, signature configuration, user association.  |

> 🔐 *Note:* Permissions also depend on the configuration of the installed license and the contracted signature module.

## Best practices

> ✅ *Recommendation:* Use easily identifiable usernames and assign only the permissions strictly necessary according to the user's profile. ⚠️ *Important:* Deleting a user does not remove their historical records or signatures already applied. To deactivate a user without deleting their history, it is recommended to disable them instead of deleting them.

## Security considerations

* Users should have strong passwords according to the security policy defined by the organization.
* Role management should be reviewed periodically to avoid unnecessary privileges.

### Additional considerations

* 📬 *Notifications:* Users may receive email notifications associated with their channels according to configuration.
* 🧩 *Specific accesses:* Each user may have access to a set of channels and contacts defined at the time of their creation.
* 🔁 *Modification:* The role can be modified later by a global administrator from the users section.

> ✅ *Recommendation:* Make sure to assign only the necessary permissions to limit security risks and operational errors.


---

# 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.editran.onesait.com/documentacion-editran/connect-v2.1-en/operacion/usuarios.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.