Content

Permissions management

This guide is intended to describe the functionality of permissions. How to interact with them, and the main aspects of permissions.


General info

Roles and permissions are the functionality that describes which actions are allowed to particular associates.

Roles — provide a way for community administrators to group permissions and assign them to users or user groups.

Permissions — define the actions that a user can perform in a community.

Level of access — is the set parameter that describes for whom the user will have access with particular permission. 

See detailed types of levels of access below:

  • none — means that the user doesn’t have access to the permission,
  • own — means that the user has access to this permission only for his profile (e.g. to see just your time off balance or projects)
  • sub — means that the user has access to the permission for his profile and profiles of all his subordinates, according to relations API
  • all — means that the user has access to interact with this permission with all in the company (e.g. to see general info and position)

Permission dependencies

Permission dependencies are the part of functionality intended to avoid loss of information because of editing information, without permission to see that information.

Here we have two main parameters for permissions:

  • The main permission — is the permission to use, which we have to set all dependent permissions (e.g. permission to Edit in HRM)
  • Dependent permission — (e.g. See associate profile, See personal info…)
The main rule to interact with permission dependencies is:

Dependent permission has to be the same or higher than the Main one (Dependent ≥ Main)

The system doesn’t allow the user to set up Main permission with a level of access lower than the Dependent one.

If you have chosen the main permission higher than the dependent one, the system doesn’t apply this change, shows you an error message and highlight all dependent permission which has to be set with the same level of access or higher than the main one. After resolving dependencies, you may set the desired level of access for the main permission.