Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Next revision Both sides next revision
en:how_to_configure_a_custom_level [2017/03/15 16:23]
127.0.0.1 external edit
en:how_to_configure_a_custom_level [2018/08/22 14:54]
ethan link to door custom admin feature (biostar2.6)
Line 2: Line 2:
  
 ====== How to Configure a Custom Level ====== ====== How to Configure a Custom Level ======
-===== Before versions before ​2.===== +The custom level feature allows you to give specified privileges to administrators in specific menus.  
-Before ​the release of BioStar 2.3, there were only operator ​levels ​for users. ​There functions were limited to their roles as shown below: ​\\ + 
-  - Administrator : full privileges over all operations +===== BioStar version ​2.6 and above ===== 
-  - User Operator ​: only full privileges ​to edit users +Custom level configuration for the monitoring section has been expanded. \\ 
-  - Monitoring ​Operator : only full privileges over the monitoring page +Refer to [[en:​how_to_configure_custom_admin_about_monitoring_section|]] 
-  - Mobile User : only privilege ​to read all menus+ 
 + 
 +===== BioStar ​version ​2.4 and above ===== 
 +In BioStar version 2.4, the custom level was further expanded to allow custom ​levels ​that controls specific ​users, devices, doors, and access groups. \\ 
 + 
 +{{:en:​2xtraining_custom_admin_007_.png?​nolink&​800|}} \\ 
 + 
 +However, be aware that the custom items only apply to its specific menu. \\ 
 +This means that even if you apply a specific user in the **User** menu item and specific devices in the **Device** menu item, the custom operator will see //all// logs of devices and users in the **Monitoring** menu because ​the settings do not apply other menus. ​ 
 + 
 +<callout type="​warning"​ icon="​true">​  
 +**Known Issue** \\ 
 +You can only add new custom levels with the default administrator (ID 1) account in BioStar 2.4. \\ 
 +Refer to the following link: [[http://​support.supremainc.com/​support/​discussions/​topics/​24000001177|Freshdesk Known Issue Forum]]  
 +</​callout>​
  
-{{:​en:​2xtraining_custom_admin_001.png?​nolink&​500|}} 
-\\ \\ 
 ===== BioStar version 2.3 ===== ===== BioStar version 2.3 =====
 In BioStar 2.3, the feature to create custom administrators was introduced. You can add a custom administrator at **Settings** > **ACCOUNT**. \\ In BioStar 2.3, the feature to create custom administrators was introduced. You can add a custom administrator at **Settings** > **ACCOUNT**. \\
Line 32: Line 44:
 {{:​en:​2xtraining_custom_admin_006.png?​nolink&​400|}} \\ {{:​en:​2xtraining_custom_admin_006.png?​nolink&​400|}} \\
  
-===== BioStar version ​2.===== +===== Before versions before ​2.===== 
-In BioStar ​version ​2.4the custom level was further expanded to allow custom ​levels ​that controls specific ​users, devices, doors, and access groups. \\+Before the release of BioStar 2.3there were only 4 operator ​levels ​for users. ​There functions were limited to their roles as shown below: ​\\ 
 +  - Administrator : full privileges over all operations 
 +  - User Operator : only full privileges to edit users 
 +  - Monitoring Operator : only full privileges over the monitoring page 
 +  - Mobile User : only privilege to read all menus. ​
  
-{{:en:2xtraining_custom_admin_007_.png?​nolink&​800|}} \\+{{:en:2xtraining_custom_admin_001.png?​nolink&​500|}} 
 +\\ \\
  
-However, be aware that the custom items only apply to its specific menu. \\ 
-This means that even if you apply a specific user in the **User** menu item and specific devices in the **Device** menu item, the custom operator will see //all// logs of devices and users in the **Monitoring** menu because the settings do not apply other menus. ​ 
- 
-<callout type="​warning"​ icon="​true"> ​ 
-**Known Issue** \\ 
-You can only add new custom levels with the default administrator account in BioStar 2.4. \\ 
-Refer to the following link: [[http://​support.supremainc.com/​support/​discussions/​topics/​24000001177|Freshdesk Known Issue Forum]] ​ 
-</​callout>​