Introduction
With regard to rights, a clear distinction must be made between roles within groups and permissions within interfaces.
- Roles are given when a user is added to a group, so the role is valid for a user in a given group.
- Permissions are given to a user for an interface (managed at the profile level), they are independent of groups.
Defining roles
Roles are used to give users differentiated rights to manage the content of a group, they are defined at group level for each user.
A user can have different roles depending on the groups they belong to.
By default a choice between 5 pre-configured generic roles is offered: Analyst, Reader, Contributor, Supervisor, Group Manager.
To find out more about generic roles you can read the article Understanding default roles.
It is also possible to create bespoke roles.
Defining a permission
Permissions are used to give users rights to administer the various interfaces. They are managed at the user profile level and are different from roles.
For each of the platforms it is possible to have different permissions.
For Accessly, for example:
- User management to create/edit/delete users
- Group management to create/edit/delete groups
- Role management to create/edit/delete roles
- Business unit management to read/edit/remove the business unit associated with a group
For a more exhaustive list of possible permissions, see the following article: What are the different permissions possible?
Conclusion
The concept of rights makes it possible to manage access to content for each user.