---
title: "Roles and permissions"
description: "The two roles in Curade Mini, Engineer and Admin, what each one opens, what an admin does and who to ask when something is out of reach."
url: https://curade.ai/en/curade-mini/docs/administration/roles-and-permissions/
product: "Curade Mini"
version: "1.0.0"
breadcrumbs:
  - "Curade Mini docs"
  - "Administration"
  - "Roles and permissions"
---

# Roles and permissions

The two roles in Curade Mini, Engineer and Admin, what each one opens, what an admin does and who to ask when something is out of reach.

Every account holds one role, set when the account is invited and changed later in the console. It decides what you can open and do, and a change takes effect at once, without signing out.

## What each role opens

| Area | **Engineer** | **Admin** |
|---|---|---|
| Dashboard | Yes, every widget category | Yes, problem widgets only |
| CLEO | Yes | Yes |
| Problems | Yes | Yes |
| Applications | Yes | No access |
| Services | Yes | No access |
| Infrastructure | Yes | No access |
| Monitoring alerts | On every page above | On problems and the health score |
| Settings | Yes | Yes |
| Console | No access | Yes, for the environments assigned to them |

Whatever the role, a dashboard shows only to you, and a chat to the people its visibility allows and to the people who run the environment ([Dashboard](https://curade.ai/en/curade-mini/docs/features/dashboard/#visibility), [CLEO](https://curade.ai/en/curade-mini/docs/features/cleo/#chats)).

An Engineer has the full monitoring depth and no console. An Admin looks after people and environments and sees the problems in them, but not the application, service and host pages.

Each role has its own colour in the app: purple for an Engineer and blue for an Admin. Of the two, only an Admin opens the console, so it shows in blue.

## What an admin does

An Admin, in the console, inside the environments assigned to them:

- invites people in **User Management** and gives them the Engineer role ([Manage users](https://curade.ai/en/curade-mini/docs/administration/managing-users/));
- updates environments in **Environment Management**, with their connection, CLEO and members ([Manage environments](https://curade.ai/en/curade-mini/docs/administration/managing-environments/));
- sends notifications to the people in them ([Send notifications](https://curade.ai/en/curade-mini/docs/administration/sending-notifications/));
- reads the CLEO chats of the users they administer there, private ones included.

An Admin cannot create or delete an environment, assign an environment to themselves, grant a role above Engineer or edit another Admin. Core Consulting staff who run the service do those, and they look after every environment.

## When something is out of reach

- An Engineer who needs a user invited, an environment connected or a notification sent asks an Admin.
- An Admin who needs a new environment, an environment assigned to them or a role above Engineer asks Core Consulting ([Get help](https://curade.ai/en/curade-mini/docs/support/get-help/)).

An Admin with no environments assigned sees a card in the console saying so, and Core Consulting assigns one.

## Monitoring alerts and roles

Monitoring alerts are personal whatever the role: each person sets their own, and nobody sets them for anyone else. An alert whose owner loses the access it needs, after a role change for example, pauses, and resumes if the access comes back. Alerts run only in environments where Core Consulting has switched them on, once the organisation has agreed.