Modifications

* A branch defines a sub-set of individuals in a tree.

* A branch defines a sub-set of individuals in a tree.

* A tree can have more than one branch, and individuals in a tree can belong to more than one branch.

* A tree can have more than one branch, and individuals in a tree can belong to more than one branch (branches can overlap).

* Branches are used in conjunction with user permissions. When permissions are set a for particular user, the user's special rights (add, edit, delete, see living) will apply only to the individuals in that branch.

* Branches are used in conjunction with user permissions. When permissions are set a for particular user, the user's special rights (add, edit, delete, see living) will apply only to the individuals in that branch.

* However, all persons in that tree, whether there are branches or not, are visible to everyone who has appropriate permissions to view that tree.

* However, all persons in that tree, whether there are branches or not, are visible to everyone who has appropriate permissions to view that tree or until they are assigned to a branch

== Why use branches? ==

== Why use branches? ==

Primarily for privacy purposes, branches label all descendants of a specific branch in the tree so that you can assign the branch to a User and allow/restrict them

Primarily for privacy purposes.

* to Edit information within their specific branch assignment

Branches restrict your Users from viewing information of living individuals they are not related to on the tree. Or to put it another way... It allows them to only view individuals they are related to.

* to view information on Living individuals within their specific branch assignment

 

* to download gedcom within their specific branch assignment (need to verify if add gedcom download to a user restricts it to that branch or whether the user can download for the whole tree)

Note - In most websites, deceased individuals are viewable to all users by default and this does not change with branches. However, when setting up your branches, you may still may want to include them so that your users with editorial privileges are able to edit their information.

 

 

 

The basic process is that once your branches are set up (See "How to Add a Branch" below), uses are then assigned to a branch during the registration process which will then restrict them to that branch. Their User privileges (also assigned during the registration process) then apply to their assigned branch.

=== Advantages ===

=== Advantages ===

* Branches provide privacy by restricting users from viewing (living)information not on their assigned branch.

* Branches provide privacy by restricting users from viewing (living)information not on their assigned branch.

* Users see more relevant information because information of living people that are not related, is filtered from viewing

* Users see more relevant information because information of living people that are not related to them is filtered out

=== Disadvantages ===

=== Disadvantages ===

They can be high maintenance...

Branches can be high maintenance...

* Branches require a high degree of awareness on the part of the administrator to know when new individuals and families are being added to the tree, so that the branches can be updated

* Branches require a high degree of awareness on the part of the administrator to know when new individuals and families are being added to the tree, so that the branches can be updated

* Having too many branches makes it difficult to determine which branches need to be updated when individuals and families are added to the tree.

* Having too many branches makes it difficult to determine which branches need to be updated when individuals and families are added to the tree.