# Profiles and habilitations
***
### What is a Profile?
Definition: set of rights.
A profile is a list of rights. Profiles are built on the basis of an interface:
* **Simplified interface** : designed for end users
* **Standard interface**: for the rest of the users (admin profiles)
***
### How do I create a profile with a standard or simplified interface?
* Go to **`Administration`** > **`Profiles`**.
* Click **`+ Add.`**
* In the **`Profile's Interface`** field, select the desired interface type.
***
### How can I list profiles with a standard or simplified interface?
From **`Administration`** > **`Profiles`**, you have two options:
1. From the search field, select **`Charasteristics - Profile's interface is Standard interface`**
2. You can also create a **personal view** to display profiles with a simplified or standard interface directly from the view:\
\
a. Click on the spanner icon\
b. Select **`Personal View`**\
c. Click on **`Create`**
d. Then select Profile's Interface in the list.
The interface type will now appear for each profile.
{% hint style="success" %}
You can make this change in the **global view** if you want it to be the default view for accounts with access to profile administration.
{% endhint %}
***
### How can I tell if an account has a standard or simplified interface?
* Go to **`Administration`** > **`Users`** > *`My_User`*, check the type of profile assigned in the Authorisations tab (list all authorisations if there are several)
* Go to **`Administration`** > **`Profiles`**
* Click on the profile(s) referenced above to see if they are in standard or simplified interface mode (you can also refer to [this question](#how-can-i-list-profiles-with-a-standard-or-simplified-interface) to display this information on the global or personal view).
***
### How do I delete or change the interface type for user accounts?
First, refer to the question above to view the profiles that have the standard or simplified interface.\
You have several options:\\
1. From **`Administration`** > **`Profiles`** > *`My_Profile`*, delete the relationship between the profile and the user:
{% hint style="danger" %}
**Warning**\
If the user does not have another profile, they will no longer be able to log in. Remember to reassign them another profile from Administration > Users. This operation must be performed by a super-admin account or an account with the necessary permissions on the root entity
{% endhint %}
2. From **`Administration`** > **`Profiles`** > **`My_Profile`**, switch the profile to the standard or simplified interface:
{% hint style="danger" %}
**Warning**\
This solution affects all users of the profile. Remember to check the list of users affected in **`Administration`** > **`Profiles`** > **`My_Profile`**, **`Users`** tab.
{% endhint %}
***
### Which profiles are created by default?
By default 8 profiles are available in GLPI:
* **Super Admin**: this profile has all rights
* **Admin**: ideal for entity administrators (no rights for general configuration)
* **Technician**: has access to the inventory and helpdesk in order to process tickets
* **Supervisor**: can perform as a Technician by adding elements allowing the management of team and its organization (allocationof tickets ...)
* **Hotliner**: it allows you to create tickets and track them, but not to be in charge of them as a technician
* **Observer**: this profile has "read" rights for inventory, management and, perhaps, observer data for a ticket
* **Self-Service**: this profile is limited to the simplified interface
* **Read-Only**: used only for "locked" objects
***
### Where can i manage profile?
* magenement is done from the **Administration> Profiles** menu
* the rights are divided into different tabs, they correspond to the "modules" of GLPI
* we advise to use the existing profiles by default and not to multiply the profiles
***
### What is an authorization?
* An **authorization** is the "connection" between **User**, **Profile** and **Entity**
* A user can be linked to one or more entities and with different rights (several authorizations)
* These rights can be passed to the daughter entities (recursive) or no.
A schematic example of delegation of rights:
***
### How to assign a authorization to a user
* The authorizations of user are managed in the "Authorizations" tab of the user's file.
* These can be added automatically via Authorization Rules (during LDAP synchronization for example).
***
### What are the differences between standard and simplified interfaces?
The profiles in GLPI (8 by default) are of two types, representing two different user interfaces:
* The **Simplified** interface
* on a default installation, only for the profile named **Self-Service**
* The **Standard** interface
* on a default installation, for all other profiles: **Super-Admin, Admin, Hotliner, Observer, Supervisor, Technician, Read-Only**
**The Simplified interface** contains a very limited menu, giving access by default only to:
* Tickets
* The reservation of equipment
* The consultation of the FAQ
* And the access to the forms of your catalog of services.
This interface is used by end-users. These users with a simplified interface **are free and unlimited**.
**The Standard interface** contains all GLPI menus (depending on the administrative rights), and is used by:
* Technicians
* "IT agents"
* Helpdesk agents
* Or even administrators, fleet managers, etc.
---
# 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://help.glpi-project.org/faq/glpi/profile_habilitation.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.