Managing the OrgChart
The following sections detail how to create and maintain the OrgChart as a product administrator .
The Bravura Security Fabric OrgChart construction process either begins with:
A list of users and no data about their relationships.
In this case, the organizational relationships must be identified and configured. You must identify the top-level manager, then either manually identify relationships, or start an Org building round.
A list of users with their organizational relationships already defined.
In this case, the organizational information was already defined on the target system and has been imported into Bravura Security Fabric . The process in this case will consist of verifying the organizational data and adjusting it if necessary.
See Mapping attributes for OrgChart management to learn how to import relationship data from a target system.
The following terms are important:
Manager | In the OrgChart, this is a user who has subordinates. |
Subordinate | This is a user who reports to another user. |
Top-level manager | This manager is the root of the OrgChart, and does not report to anyone. |
Org building round | This is a server-driven process that invites managers to name their subordinates in a top-down sequence. Managers login to Bravura Security Fabric to identify their subordinates and which of them are managers themselves. The process cascades down until all levels of management have been involved. You can start Org building rounds to initially build the OrgChart, or to periodically verify data. |
