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
Next revision Both sides next revision
en:how_to_configure_a_custom_level [2018/10/11 14:39]
conan
en:how_to_configure_a_custom_level [2018/10/19 12:56]
conan
Line 22: Line 22:
 Depending on such privilege settings, "Add Button"​ column value will be changed (N/A, Disabled, or Enabled)\\ Depending on such privilege settings, "Add Button"​ column value will be changed (N/A, Disabled, or Enabled)\\
  
-**Dashboard** only allows ​"Read" ​privilege and its "Add Button" will show "​N/​A"​ status\\ +<callout type="tip" ​icon="true"
-When the "​Read"​ is checked ​the dashboard will be shown when you log in to BioStar 2. \\ +  * The expansion of Admin Item Settings to universal setting of the Custom Level will influence the Admin Menu Settings
-Depending on Admin Item Settingsdashboard use status is not supported but is shown by the number of use status according ​to 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 main administrator had privilege to access this feature)  
 +  * If you are upgrading from previous versions ​to BioStar 2.6.3you need to perform migration on the Custom Level 
 +  * The Administrator will receive alert regarding Custom Level activities 
 +</​callout> ​  
  
-**User** menu sets who can see the user menu depending on the privilege that is set here. The privilege ​to this menu is affected by User GroupAccess Group, and Device Group. +Up to BioStar 2.6.2Admin Item Settings were only limited to Monitoring section as in the screenshot below.\\
-  * User Group: Add/Edit privilege limit on a menu +
-  * Access Group: Display/​Select privilege limit on a user specific page +
-  * Device Group: Device display privilege limit when enrolling fingerprint/​face/​card for a user+
  
-**Device** menu dictates display privilege of Device menu depending on its "​Edit/​Read"​ setting.\\ +{{:en:biostar2_custom_level_2.png?​nolink&​1200|}} ​\\
-Device menu privilege is affected by User Group, Device Group of Admin Item Settings. User Group influences administrator Display/​Add/​Edit privilege limit of a device specific page. For an administrator who does not have privilege to a device is set, an administrator who does not have privilege is displayed when entering a device specific page, and this can be deleted. \\ +
-  * Device Grouplimits display of a device on a menu, and limits device Add/Edit privilege \\+
  
-**Door** menu dictates display limit of a Door menu depending on its Door menu Edit/View privilege settings.\\ +Below can be an example ​of how you can realize features that are changed in 2.6.3
-Door menu privilege is affected by Admin Item Settings(whether set to Device Group, Door Group, and Access Group) +
-  * Device Group: limits Display/​Add/​Edit privilege of a Door specific page +
-  * Door Group: limits Display/​Add/​Edit privilege of Door on a menu +
-  * Access Group: limits ​ \\+
  
-**Access Control** menu dictates display limit of elevator menu depending on Edit/​Display privilege settings.\\ +<callout type="​primary"​ icon="​true">​ 
-Access Control menu is affected by Admin Item Settings(User Group, Door Group, Access ​Group). +  ​Employee name: Max 
-  * User Group: ​User Display/​Add/​Edit limit on an access group specific page +  ​Employee group(User Group): IT 
-      * Can only Add users with privilege +  * Device used when entering from the main entrance(Device ​Group)BioStation L2 
-      * Can only Delete users when an user is added to an Access Group without privilege within a created Access Group +  * Working Space(Door Group)IT Main Office A1 
-  * Door Group: ​Door Group Display/​Add/​Edit limit on a menu +  * Department(Access Group)IT Department 
-  * Access Group: ​Dual Authentication Add/Edit limit on a Door specific page +</callout>  ​
-      * All Groups: Can Create/Edit/Delete Access Group and Elevator Group +
-      * Specific User Group: Can Add/Delete an User Group or an User with privilege, within an Access Group(does not include Access/​Elevator Level) \\ +
  
-**Monitoring** dictates display of Monitoring menu depending on Edit/Read settings. \\ +Admin Item Settings and Admin Menu Settings ​can be properly configured ​to reflect ​the example above.\\
-Monitoring menu privilege is affected by all items in the Admin Item Settings+
-  * Event/​Real-Time Log +
-      * Only devices with privilege in the device ID by default can be filtered, ​and the filter cannot be deleted +
-      * Filter cannot be set for Device and Device Group(because device filter is applied to a device with privilege for logs) +
-      * Upper right-hand corner option is displayed only when with Edit privilege settings +
-  * Device Status +
-      * Device is displayed according to Device Group privilege settings +
-      * Device Alarm Enable/​Disable is displayed only with Edit privilege settings +
-  * Door Status +
-      * Door is displayed according to Door Group privilege settings +
-      * Door control is possible and option buttons ​can be displayed depending on Edit privilege settings +
-  * Elevator Status +
-      * Elevator is displayed according ​to Elevator Group privilege settings +
-      * Elevator control is possible and option buttons can be displayed depending on Edit privilege settings +
-  * Zone Status +
-      * All of the zones can be displayed +
-      * Zone control(alarm clear) is possible and option buttons can be displayed depending on Edit privilege settings +
-          * Access Denied popup is displayed when a zone tracking window cannot be displayed due to no privilege to access added devices to the zone\\  +
-  * Alert Status +
-      * Alert popup is displayed when Monitoring Edit/Read privilege is set(Alert popup is only displayed for device IDs with the privilege settings).\\ +
-      * With Monitoring Read privilege only, a confirm button for an alert is not displayed and can only be ignored, alert history can be checked, and alert list can be displayed and the checkbox is enabled to allow creating and checking memos. \\ +
-  * Real-time Videos +
-      * Videos can be displayed depending on Video privilege(Edit/​Read) settings +
-      * Videos are not displayed if no Video privilege is set +
-      * The Door Control is affected by Door Group of Admin Item Settings set to Video camera of Real-Time video when Monitoring Edit privilege is set \\+
  
-**Time ​and Attendance**  +1. Because Max belong to IT Department, we can setup Access Group and Access Level via Access Control menu.\\ 
-  * The same way as 2.6.2 works (is not affected by Admin Item Settings)+{{:​en:​custom_level_-_1.png?​nolink&​800|}} \\
  
-**Settings** +2. When Creating Access ​Group, ​you will be prompted to create Access Level \\ 
-  * Only Preferences and Https are displayed if Settings menu Edit/Read privilege is not set +- Assigning a user will not be necessary as we will assign a user to a specific user group\\ 
-  * Settings menu Read privilege +{{:​en:​custome_level_-_2.png?​nolink&1000|}} ​\\
-      * Everything is displayed except Account menu +
-      * No Video menu should be displayed in the Settings for Accounts with only Settings privilege  +
-      * Device display limit of server, working conditions, and face group-matching depending on Admin Item Settings (User Group, ​Device Group, and Door Group) ​\\ +
-  * Settings menu Edit privilege +
-      * Everything except Accounts menu is displayed, and Add/Edit is possible for each menu of the Settings +
-      * Video menu of the Settings should ​not be displayed for accounts with only Settings privilege +
-      * Device display limit of server, working conditions, and face group-matching depending on Admin Item Settings (User Group, Device Group, and Door Group) ​\\ +
-  * Video +
-      * Video menu is displayed depending on Settings menu Read/Edit privilege ​Video Read/Edit privilege(Video display of the Settings with Video Read/Edit privilege, Video on Settings operate depending on Read/Edit privilege settings)  ​\\+
  
-<callout type="tip" ​icon="​true">​ +3. Let's go to Door menu to setup Door Group, right click on All Doors and click "Add Group" to add Door Group \\ 
-  * The expansion of Admin Item Settings ​to universal setting of the Custom Level will influence the Admin Menu Settings. +- You can see the Door Group created below it, here it is named to IT Main Office A1\\
-  * The Account button ​can only be visible to the Administrator. +
-  * If you are upgrading from previous versions ​to BioStar 2.6.3, you need to perform migration on the Custom Level +
-  * The Administrator will receive alert regarding Custom Level activities +
-</​callout> ​  +
  
-Up to BioStar 2.6.2, Admin Item Settings were only limited to Monitoring section as in the screenshot below.\\+{{:​en:​custom_level_-_3.png?​nolink&​1000|}}
  
-{{:en:biostar2_custom_level_2.png?​nolink&​1200|}} \\+{{:en:custom_level_-_4.png?​nolink&​1200|}} 
 + 
 +4. Now move on to Device Tab and just as we've done it, right click on All Devices to click "Add Device Group" \\ 
 +- You can see the Device Group created below it, here it is named to BioStation L2(IT) \\ 
 + 
 +{{:​en:​custome_level_-_5.png?​nolink&​1000|}} 
 + 
 +5. Click the device, and then assign its group. \\ 
 + 
 +{{:​en:​custome_level_-_6.png?​nolink&​1200|}} 
 + 
 +6. Let's go to Settings -> Account -> Add Custom Level \\ 
 +{{:​en:​custom_level_-_8.png?​nolink&​1000||}} 
 + 
 +7. Here it will be named IT, and we will set all of the Admin Item Settings that we created previously \\ 
 +- We will create User Group in the next step, and then you can come back to this menu to assign the created User Group. \\ 
 +- This user will only have "​Read"​ rights for all of the Admin Menu Settings \\ 
 +{{:​en:​custom_level_-_9.png?​nolink&​1200|}} 
 + 
 +8. Finally, let's create a user by going to User menu \\ 
 +- Likewise, right click on All Users and click "Add User Group",​ here it is named "​IT"​ \\ 
 + 
 +{{:​en:​custome_level_-_7.png?​nolink&​1200|}} 
 + 
 +9. Add a new user and set appropriate Group(User Group), Operator Level, and Access Group that we just created. \\ 
 +- set the Login ID and Password that you can remember well 
 +- at this point you can go back to step 7 and assign the created custom level to the user group that this user has set \\ 
 +-> this will automatically set the user Max to be accounted for the custom level \\
  
 +{{:​en:​custom_level_-_10.png?​nolink&​1200|}} ​
  
 +10. Now when you login as Max
 ===== BioStar version 2.4 and above ===== ===== 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. \\ In BioStar version 2.4, the custom level was further expanded to allow custom levels that controls specific users, devices, doors, and access groups. \\