This article is intended for administrators.

⚠️ Please note: This feature is associated with a specific billing, so please contact your Customer Success if you would like to know more about it.

• 📍 When is the MLA option useful?
• 💡 How to define roles limited to a user segment?
• ⚙️ How does it work?
• 🎛 How to set it up?
• 👩🏻‍🎓 How does this work for the Training product?

Before continuing your reading on MLA, we recommend you consult the article dedicated to roles and permissions in general: Managing administrator rights: roles and permissions

📍 When is the MLA option useful?

Roles and permissions allow you to define a set of permissions (actions) for a user. The MLA option takes this a step further, allowing you to limit this role to a segment of your population.

Here are some examples of situations that can be handled with this feature:

• A member of the HR team manages the R&D department but not the Sales department
• One member of the HR team manages interviews and training for entity A, but only interviews for entity B,
• One member of the HR team manages all employees except the Executive Committee and CEO
• A Business Unit Director wishes to manage and launch his review cycles within his entity

This way you can ensure that only authorized persons have access to content related to certain users (evaluations, objectives, feedback, etc.)

⚠️ Warning : The implementation of this option does not make 2 entities completely hermetic. For example, if you decide to launch a 360° feedback review cycle, employees from entity A can select employees from entity B as peers.

💡 How to define roles limited to a user segment?

With advanced management of administration rights (MLA), you can define these roles for the entire population, or just a segment of it. This segment is called “Entity”.

These roles are detailed in the following article: Managing administrator rights: roles and permissions

In order to assign rights by sub-population, the first task is to divide users into Entities. Each user can be placed in one (and only one) entity, with no hierarchical limitations.

Once the MLA option has been activated and set, a new field will appear on the role assignment modal, allowing you to limit the role to one or more entities.

⚙️ How does it work?

Let's take a simple example: a company with a CEO, a Comex, and departments under each COMEX member.

The example above shows 4 examples of Entities (here they follow the hierarchies, but entities can be transversal).

Example 1️⃣: Admin role assignment.

In this first example, each entity is managed by one of the HRs, the COMEX users, and the HRs are managed by the HRD.

Example 2️⃣: Admin role assignment.

In this second example, HR1, who manages HR2 and HR3, also has access to the management of the entities administered by his team. The administration of COMEX and HR1 is reserved for the HRD.

🎛 How to set it up?

We invite you to contact your Elevo expert or the Support who will redirect you to the person in charge of your account.

👩🏻‍🎓 How does this work for the Training product?

💡 Please note that the Training Product is an add-on product that must be activated on your space in order to be used. Contact your dedicated Customer Success to learn more.

Session management

• They can only see requests from their administered entity’s users and they can create sessions in order to link them to it.
• They can add requests to an existing training session:
  • if the session has been create by a MLA in the same admin group (or the MLA themselves),
  • if the session has been created by an org admin.
• They cannot add requests to a training session created by a MLA from another admin group.
• They can only edit the sessions they have created (training details, training session planning).

Invite to a session

• If they are the session creator, they can send invitation/cancellation to all the participants (even the ones they don’t administer),
• if they are not the session creator, they can only invite their administered users.

Participants visibility

• Entities admins can only see participants that they administer,
• They can edit the funding/approval status of their administered users only,
• They can only remove participants they administer.

Deletion

They cannot delete a session, whether it be :

• from the session itself, the button is not displayed.
• from the session screen, the row menu is greyed out and non clickable.