Functional overview > Concept > Relationship between the main branch and its sub-branches

Relationship between the main branch and its sub-branches

Changing the branch name

For changing the name of the main branch from the default name ("company"), see Editing the name of the "company".

Concept

For configuration of the main branch and the sub-branches, the user must have the administrative rights for all relevant branches. For administrative rights of a sub-branch the user has to be assigned to the sub-branch or to the main branch.

Like the main branch, sub-branches can contain entities that are constricted to the branch itself. Entities of the main branch cannot be configured from the sub-branch.

Entities, such as maps, cameras or layers, are either configured with the CoreServiceMaster (CSM) of the main branch for all CoreServices. The entities thereby "refer" to a server (CSM or CSS). Basically, only references in the sub-branch, or from the main branch to the sub-branch are allowed. There are no references between sub-branches.

For the relationship between CSM and CSS see Relationship between the CoreServices - master and slave.

The only exception for references from the CSS to the CSM are cameras and Device Management servers, where the camera of a sub-branch can be managed through the Device Management server of the main branch, thereby relieving sub-branches of installing their own Device Management server.