> For the complete documentation index, see [llms.txt](https://docs.transparentedge.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.transparentedge.eu/getting-started/dashboard/user-management.md).

# User management

To access the User Management section, click on the icon that depicts a user, located at the bottom of the side panel.

From this section, you will be able to change user permissions within the company, edit their information, delete user profiles, or create new users. You can also view the permissions associated with each user and check if they have enabled 2FA (Two-Factor Authentication).

### Edit User

Any user within the company can be edited, and also deleted, using the buttons located on the right-hand side under actions. 

From the pop-up window, you can edit the user's first name, last name, and password, as well as the associated permissions that grant access to different actions and sections of the dashboard.

<figure><img src="/files/swUp3pLdHBlmy4NdhjN0" alt="" width="563"><figcaption></figcaption></figure>

### Create New User

The process of creating a new user is very simple. The button to do so is located in the upper right corner.

<figure><img src="/files/LC9ZU3ToG0rekmh7fvvH" alt="" width="563"><figcaption></figcaption></figure>

Once the modal is displayed, you need to complete the required information: the email of the new company member, their first name, last name, the permissions they will have associated with their account, and assign them a password that the new user can later change.

After completing all of this has been done, the new user will receive an email in their inbox with all the information needed to access the dashboard. The company administrator will be able to manage all user information from the 'User Management' section.

### Permissions

**Company Administrator:** Full access to all company resources, settings, and user management.

**Invalidator:** Allows managing cache invalidation by URL or tag, as well as cache warmup operations.

**Statistics:** Read-only access to metrics dashboards and service performance data. Users with this role can consult analytics and historical data.

**Config Administrator:** Full configuration management of services: sites, backends, cache rules, DNS, SSL, autoprovisioning, and bot mitigation.

**Storage:** Manages storage buckets, their content, and consumption tracking.

**Transcoding:** Accesses and manages transcoding profiles, video jobs, processing queues, and consumed minutes.

**Log configuration:** Manages log configuration, storage destinations, and streaming setup.

**Staging:** Manages staging backends and autoprovisioning configurations.

**DNS Management:** Manages DNS zones, records, domains, hooks, and SSL certificates.

**Read-only access:** Read-only access to all company resources and configurations.

**IP list management:** Manages IP allow/deny lists, network blocks, address ranges, and notification preferences.

**Notifications only:** Manages notification preferences, alerts, and account security settings.

**User Administrator:** Allows creating and managing users within the company.


---

# 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.transparentedge.eu/getting-started/dashboard/user-management.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.