The Operators Permissions feature allows you to create software users and operator groups. You can then assign different permissions to the groups, (so that certain features can be hidden/shown for the different users). User account types can be restricted to view only certain controllers and/or only certain access groups. Routes can also be assigned so the software users will only be able to see events generated from hardware that has that same route(s) assigned to it. Users can also be set audit permissions.
The software supports an unlimited number of additional users and user groups, however, the number of users that can connect at any one time is dependent upon the Application Server's client license count. The standard Doors.NET software includes one licensed client connection.
The second tab is Permissions. The software uses a combination of database rights and account types to control what an operator can 'see' when they login. The permissions tab in Operator Setup controls the display of menus (i,e hide the buttons on the main toolbars). Application Permissions are then applied to settings within those menu items. The Permissions are most commonly used to cut down on the number of menu items shown.
In addition, if a credential is highlighted in a cardholder record you will notice that it's also not possible to change the status.
The Locations tab configures which controllers the user group is allowed to manipulate. Those that are unchecked will not be shown to any login in that user group. In the example below, the Security Management user group will only see the first PXL500 controller listed on the London Office PXL gateway. It will appear to them as though there is only 1 PXL on the gateway when in fact there are two. By not being able to 'see' the second controller, the logins in this user group will not be able to configure, override, receive messages, or run reports on the second PXL500.
The third part of the virtual database permissions is the Access Groups tab. The system administrator must assign access groups to a user group. This controls what is shown in the access group and cardholder menus. In the access group menu, the list of available access groups will be the ones the system administrator has assigned. They will also be the ones available to assign access rights to a cardholder in the cardholder menu, and they will be used when the user searches the cardholder database. For example, suppose the cardholder database has 100 entries with the last name of 'Smith' and of those 30 are assigned to an access group named "Executives." When a user in the Security Management user group performs a search for cardholders with the last name of 'Smith', only those 30 records will be shown in the search results. This is because the other 70 cardholders do not have an access group assigned that is in the available access groups for the Security Managers.
In addition to controlling which hardware items are available through Location assignment, and the search limits imposed by the access group assignment, the user group can also be assigned one or more routes. A route is part of the event message notification and only user groups that have a route assigned can receive messages from the hardware which also has the same routes assigned. This allows the system administrator to configure a user login that receives messages from just a selection of hardware (i.e from certain readers in certain locations).
The Audit section in Operator Permissions allows you to view all of an operator's login sessions and activity. This is viewed by user, not by user group.