Managing User Visibility and Permissions

When creating a new user, it is necessary to define a visibility level and a permission for each one. In the “User” tab, click on “View details”:

The Total on my company visibility gives full access to all company resources, with no restrictions on internal data. The Limited to my resources visibility restricts access to only the resources associated with that user.

The ADMIN permission allows full management of the platform. It enables the creation of users, learning paths, applications, and the management of reports. The SUPPORT permission grants read-only access to all APIs. It allows data consultation without authorizing any modifications. The USER permission allows the creation of enrollments, consultation of the user list, and retrieval of data from those enrollments. The APP permission is a technical permission. It must not be assigned to a user. It is reserved for internal use by applications and systems.

To ensure secure and consistent platform management, we recommend the permission and visibility combinations described below. Each combination has been defined to match a specific use case and to limit access to the strict minimum required for the user's profile.

• Create learning paths, applications and enrollments
• Create and list users / administrators
• Create themes
• Read/write access to all resources (applications, reports, companies)

• View themes
• Read-only access to all resources (applications, reports)
• ✘ Cannot create learning paths, enrollments or applications
• ✘ Cannot add users
• ✘ Cannot edit their own profile

• List platform users
• Edit their own profile
• View themes
• Create enrollment links for existing learning paths
• Read access to the reports of all applications and all users
• ✘ Cannot create applications
• ✘ Cannot add users

• List platform users
• Edit their own profile
• View themes
• Create enrollment links for existing learning paths
• Read access to the reports of enrollments they created only
• ✘ Cannot create applications
• ✘ Cannot add users

Both USER profiles share the same action permissions, only the scope of visibility differs: one can see all platform resources, the other can only see their own.