To be able to manage roles the user should have the ‘Administrator’ role. Without this role the user won’t be able to see the roles (unless they have the permission to update user roles), update or delete roles.
Adding new roles
To create a role you have to navigate to the ‘roles’ screen. At the top left of this screen you’ll find an ‘+ Add role’ button. To start creating a new role you press this button. This will take you to the 'Add new role' overlay where you can fill in the details and allowed permissions for the new role.
In the first step you fill in for which organization this role is created (by default it is created for the current organization), what the name of the role is, what the short description is for the role and if the role should be propagated to all sub organizations. Note that when propagating a role it can only be made unavailable when no users from sub organizations have the role. The minimum that needs to be filled in here is the organization and the name for the role. After you’ve filled in the details you can press the ‘Next step >’ button.
In the second step you fill in which permissions the new role will have. By default some of the permissions are checked and disabled these are the read permissions for organization, location, asset, user and pass. These permissions currently don’t affect anything in our system but are mainly shown to let the user know which things are accessible by default with a role. After you’ve selected the desired permissions you can press the ‘+ Add role’ button at the bottom of the screen.
After this you should be back on the roles screen and get a green success pop-up to let you know that the new role has been created. This pop-up contains a link to the new role that, once clicked, opens the respective modal for the newly created role. If something went wrong for whatever reason you’ll stay on the second step of the 'Add new role' overlay and see a red error pop-up.