Roles and Permissions in the eADM

To use the eADM , each user must be assigned a role. This role determines what you can view and do within the system by placing you in a permission hierarchy.

eADM permission model is based on six distinct roles. In this hierarchy, each role inherits all the permissions of the roles below it.

The six roles are:

• Employee

• Superuser

• Manager

• Service Desk User

• Administrator

• Partner Administrator

A Closer Look: Service Desk vs. Administrator Roles

Although there are six roles, many users interact most frequently with the Service Desk and Administrator roles. Understanding the difference is key to knowing who can assist you and what changes they can make.

The Service Desk User Role

Think of the Service Desk User as a role designed for user support and day-to-day administration. This role can view all user information and perform key administrative tasks, such as managing passwords and permissions, but does not have access to core system configuration.

Key Permissions and Capabilities:

• View All User Information: A Service Desk user can search for and view the details of any user account within their organization. This is useful for troubleshooting and answering questions.

• Change Passwords for Users: They can reset passwords for other users in the organization.

• Manage User Permissions: They can manage access permissions for users.

• View Organizational Structure: They can view details about departments, groups, and the organization's overall profile.

• No Core Configuration Changes: A Service Desk user cannot modify the core settings of eADM, such as synchronization rules or system integrations.

This role is ideal for help desk staff and junior administrators who handle day-to-day user management tasks but are not responsible for the overall administration of the eADM .

The Administrator User Role

The Administrator User has nearly full access to all features and settings within a single organization in eADM. This role is intended for trusted individuals who manage the configuration and security of the identity system.

Key Permissions and Capabilities:

• Full User and Group Management: An administrator can perform all the actions of a Service Desk user.

• System Configuration: Administrators can configure all core aspects of the eADM for their organization. This includes managing the organization profile, synchronization rules, message templates, and access control settings.

• Assigning Roles: An administrator can add or remove permissions for other users up to and including their own permission level. For example, they can assign the Manager or Service Desk role but cannot assign the Partner Administrator role.

This powerful role is typically reserved for senior IT staff responsible for managing the organization's identity and access platform.

Comprehensive Permissions Table

Please refer to the official permissions table for information on what each role can and cannot do within the application:

Important Rules and Conditions

The permissions listed above are subject to the following conditions:

User Access Scope

• Limited Scope: Superusers and managers can only perform actions (such as changing passwords) on users who belong to the specific groups and departments to which they have been granted access.

• Full Scope: Service Desk users and administrators can view and manage all users across their entire organization.

Assigning Permissions

A user can grant or revoke permissions for other users, but only up to their own permission level.

Definition of "Organization Details"