The User Admin module contains the functions required to administer users within the organisation tree (which can consist of one or many organizations). User admin is comprised of Users, Roles and Security groups.
On-Road IoT makes use of security groups and roles in the following way:
- Users are put into a security group.
- Permissions and access rights are assigned to the security group through the use of roles.
- Users inherit the rights assigned to the security group.
If a group of users all require common access to a function, instead of applying permissions to every user, apply permissions to a security group and ensure that the users are members of the security group.
The security group determines what can be accessed, such as assets and drivers. The security group depicted above gives access to a group of assets only.
The role unlocks the permissions and dictates what actions can be carried out on the assets or drivers, e.g. the group of users depicted above may be able to view and edit asset details.
The user is the one within the security group who is accessing assets and performing the actions, e.g. editing the asset's details.
For example, a security group is created with access to assets, a role is created with permissions to access and edit assets. Individual users are made members of the group. The users inherited the security group permissions so these users now all have access to the assets and they have permissions to edit the assets. This implies that if a group of users all require common access to a function that instead of applying permissions to each user you just have to apply the permissions to the security group.
Best process to create users
- Create the roles.
- Create a security group.
- Assign a role to the security group.
- Create the users.
- Add users to the security group.
When creating a user or security group or a role, you will need to specify where in the organisational structure the entity fits, meaning who can see the entity.
NOTE: An entity lower down in the tree cannot view an entity higher in the tree.
|
Step 1 Create a role and specify what permissions this role will have: Example: Create role “Basic Tracking User” with access and update permissions for the Fleet Tracking Module. |
If administering multiple organizations, select at which level this role will be accessible. |
|
Step 2 Create a security group, specify to what the security group has access, and allocate the created role to the security group. Example: Create a security group called “Fleet Tracking-Mark Salon” and specify which assets in the tree the users of this group will be able to see. Now assign the role Basic Tracking User to the security group, which gives the users of the group "Fleet Tracking-Mark Salon" security group access to view the assets in the organisation selected. |
If administering multiple organizations select at which level the security group will be accessible. |
|
Step 3 Create a user and assign the user to a security group. Example: Create user John and allocate John to the Fleet Tracking-Mark Salon security group. |
If administering multiple organisation select at which level the user will be accessible. |
|
Result User John is able to access the Fleet Tracking module and perform access and update functions available within this module. |
|