Understanding the hierarchy
The Groups constitute the hierarchy of your enterprise.
Here is an example of the Enterprise Hierarchy:
 |
Note
NewCorp Inc. is also considered as a Group. This Group is at the root of the Enterprise.
Significance of Hierarchy and the Principle of Visibility
The Principle of visibility in Fieldlogs follows three rules:
Parent groups can see data of the Child groups. Users of Parent group can access the Template DB, Publish Templates and view the Lifecycle of the Child group.
In the example shown above, NewCorp Inc is the Root Group. Aviation is the sub Group of the Root Group.
Aviation is also the Parent Group of Engineering and Aviation Operations Child Groups. Aviation can see data of the Engineering and Aviation Operations.
Child groups cannot see data of their Parent group. Users of Child groups do not have access to the Template DB, or cannot Publish Templates associated to the Parent Group.
In the example shown above, 1 ,2 & 3 are Parent groups, 2, 3, 4 & 5 are Child groups.
Contractor 1 & Contractor 2 cannot see the data of Oil&Gas Operations and Oil&Gas.
Operations cannot see the data of Special Projects.
Groups at the same hierarchy level and their child groups cannot see each other's data.
In the example show above , A user in the group Contractor 1 creates a Template.
Users in the groups Oil&Gas, Oil&Gas Operations and Contractor 1 can see this Template. But the users in the groups Contractor 2, Product Operations and Special Projects cannot see this Template.
Similarly the users in the groups Aviation, Engineering, Aviation Operations which are in the same Hierarchy level also cannot see this Template.
The Root Group NewCorp Inc can see all the parent and child groups Template DB.