What is a Subsystem
Subsystems are separate groups of administrators, personnel, locks and other system components. They may be used to separate visibility and operations from one part of a CyberAudit-Web system to another.
One example of using subsystems might be an international company that has locations in different countries where each division of that company wants to independently manage their part of the system.
The top level management wants access to every aspect of their security system and the key issuers for each division should not see people and locks that are not part of their division. Subsystems provide this functionality. Top level management can see the whole system while administrators at different subsystems see only the locks and people that either originated in their subsystem or whose visibility was added to their administrator node in their subsystem.
People and locks may be seen by administrators of different subsystems if they are copied or moved into them. This means an administrator can see a person that originated in another subsystem but not the keys issued to the person. They can, however, issue keys (or missions) that belong to their subsystem to the person.
Another example might be a company where each division observes different holidays. Because subsystems hide visibility of holidays, keys that should not operate on a holiday in one division won't affect the keys in another where it is not a holiday.
| Items Governed by Subsystems | Items Not Governed by Subsystems |
|
|
|
Why use Subsystems?
|
|
