Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:how_to_configure_a_custom_level [2018/01/03 13:10]
ethan title (and above) 추가
en:how_to_configure_a_custom_level [2022/11/01 14:57] (current)
sungjun [BioStar version 2.6 and above]
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 4 operator levels ​for usersThere 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 +From BioStar 2.6.3, the Admin Item Setting is changed so that a custom level can be assigned ​for a specific User Group, Device Group, Door Group, and Access GroupAlso Monitoring menu is now allowing the administrator ​to assign "​Read"​ rights. \\ 
-  ​- Monitoring Operator ​: only full privileges over the monitoring page + 
-  - Mobile User : only privilege ​to read all menus. ​+1. Go to the **Settings** > **ACCOUNT**. \\ 
 +{{:en:​biostar2_custom_level_1.png?​nolink&​800|}} ​\\ 
 + 
 +2. Create new Custom Level. At this point, you can configure the item settings and menu settings. \\ 
 +{{:en:​custom_level_-_2.6.3.png?​nolink&​1000|}} \\ 
 + 
 +You can also see now that the Monitoring Admin Menu Setting allows "​Read"​ assignment.\\ 
 + 
 +**Admin Item Settings** includes User Group, Device Group, Door Group, and Access Group(including Elevator Group). \\ 
 +Each item can be configured for each group or for all groups. \\ 
 +**Admin Menu Settings** consists of Dashboard, ​User, Device, Door, Elevator, Zone, Access Control, Monitoring, Time and Attendance, Setting, and Video categories. \\ 
 +For each menu you can set "​Edit"​ and "​Read" ​privileges. \\ 
 +When checking "​Edit"​ it will automatically check "​Read."​ \\ 
 +Depending on such privilege settings, "Add Button"​ column value will be changed (N/A, Disabled, or Enabled)\\ 
 + 
 +<callout type="​tip"​ icon="​true">​ 
 +  * The expansion of Admin Item Settings ​to universal setting of the Custom Level will influence the Admin Menu Settings. 
 +  * The Account button can now be visible to all users that have administrator privilege as opposed to the previous versions in which only the default administrator(with User ID: 1) had privilege to access this feature. ​ 
 +  ​* Up to BioStar 2.6.2, custom level administrators could not receive alerts but they can now receive alerts in BioStar 2.6.3 and above.  
 + 
 +</​callout> ​   
 + 
 +To see an example of this change please refer to [[en:how_to_configure_a_custom_level_example_for_2.6.3|]] 
 + 
 +Up to BioStar 2.6.2, Admin Item Settings were only limited to Monitoring section as in the screenshot below.\\ 
 + 
 +{{:en:​biostar2_custom_level_2.png?​nolink&​1200|}} \\ \\ 
 + 
 +{{ :​en:​how_to_configure_a_custom_level.mp4?​900x506 |}} 
 +===== 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 71:
 {{:​en:​2xtraining_custom_admin_006.png?​nolink&​400|}} \\ {{:​en:​2xtraining_custom_admin_006.png?​nolink&​400|}} \\
  
-===== BioStar version ​2.4 and above ===== +===== 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>​+