Difference between revisions of "V2/Concepts/User/Role"
From Senfi Docs
(Created page with "<h1 class="main-heading">Role</h1>") |
Elysia.Tan (talk | contribs) |
||
(13 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
<h1 class="main-heading">Role</h1> | <h1 class="main-heading">Role</h1> | ||
+ | |||
+ | Within an organization, roles are created for various job functions. The permissions to access modules and perform certain actions are assigned to specific roles. A role can be assigned to one or several users, and each user can only have one role. | ||
+ | |||
+ | The module access and actions that can be assigned to a role are: | ||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | !Module | ||
+ | !Read | ||
+ | !Create | ||
+ | !Update | ||
+ | !Delete | ||
+ | |- | ||
+ | !User | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | |- | ||
+ | !Site | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | |- | ||
+ | !Asset | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | |- | ||
+ | !Measurement | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | |- | ||
+ | !Video | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | |- | ||
+ | !Automation | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | |- | ||
+ | !Developer | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | | | ||
+ | |- | ||
+ | !Alarm | ||
+ | | | ||
+ | | style="text-align: center; background-color: lightgrey; color: white;"| | ||
+ | | | ||
+ | | style="text-align: center; background-color: lightgrey; color: white;"| | ||
+ | |- | ||
+ | |} | ||
+ | |||
+ | Each [[V2/Concepts/User/Organization|organization]] has a default role called '''Administrator''' that can perform all actions. The Administrator role cannot be edited or deleted, and there must be at least one user in an organization with the Administrator role. | ||
+ | |||
+ | [[File:Concepts_User_Role.png|center|thumb|800px|Example of Organization, Role & Actions|link=]] | ||
+ | |||
+ | Users with the Administrator role are able to manage other roles. | ||
+ | |||
+ | <div class="important">Note: If user A has role B, and role B is deleted, user A will be assigned an empty role and will no longer be allowed to login. The Administrator or someone who can manage users will need to assign a new role for user A before he/she can login.</div> | ||
+ | |||
+ | ==== What's Next ==== | ||
+ | ----- | ||
+ | * [[V2/Concepts/Preparing for Role Creation|What is needed to create a Role]] | ||
+ | * Start [[V2/CMS_Tutorial/User_Tools/Creating_Content/User/Role|creating your own Role]] | ||
+ | * Learn about [[V2/Concepts/User/Access_Group|Access groups]] |
Latest revision as of 18:44, 6 August 2021
Role
Within an organization, roles are created for various job functions. The permissions to access modules and perform certain actions are assigned to specific roles. A role can be assigned to one or several users, and each user can only have one role.
The module access and actions that can be assigned to a role are:
Module | Read | Create | Update | Delete |
---|---|---|---|---|
User | ||||
Site | ||||
Asset | ||||
Measurement | ||||
Video | ||||
Automation | ||||
Developer | ||||
Alarm |
Each organization has a default role called Administrator that can perform all actions. The Administrator role cannot be edited or deleted, and there must be at least one user in an organization with the Administrator role.
Users with the Administrator role are able to manage other roles.
Note: If user A has role B, and role B is deleted, user A will be assigned an empty role and will no longer be allowed to login. The Administrator or someone who can manage users will need to assign a new role for user A before he/she can login.
What's Next
- What is needed to create a Role
- Start creating your own Role
- Learn about Access groups