Difference between revisions of "Branches"
Line 8: | Line 8: | ||
==What the user sees== | ==What the user sees== | ||
+ | |||
+ | In a Branch system, the User Account Details page has an extra tab called "Branches". | ||
+ | |||
+ | [[File:Branches_1.png|border]] | ||
+ | |||
+ | |||
+ | From this tab you can set the view permissions for the user. Options for which branches they are allowed to view are: | ||
+ | |||
+ | * All branches | ||
+ | * Individual Branches (tick/select every branch you want this user to be able to see) | ||
+ | * [[Branch Groups|Groups of Branches (Views)]] |
Revision as of 14:03, 7 August 2015
In standard form, Charitylog customers can share details of all of the organisations/people they deal with across all of their staff. Work done with those people can be restricted from users on a per-user basis, but every user of the system can always see all the organisations and people on that system. However, some customers actually don't want things to be this open - they want to have some way of restricting the visibility of the organisations/people themselves so that only certain members of staff can see that they even exist. This happens most commonly in partnership organisations or consortia, where the system is actually used by several separate customer organisations. The partnership/consortium want the benefits of a standardised system, and the ability to report on everything at once, but with control of what users can see.
Charitylog's Branches module allows this. You can set up as many Branches as you require, and then put organisations/people in one or more branches. Each user is also allowed access to one or more branches. The user will be able to see only the organisations/people in the branch that they are currently logged into. Administrators control both the visibility of organisations/people, and the access permissions of users, thereby making sure that users only see what they should see.
There is great flexibility available with the Branches module, and this means that the setup of a branch system is quite involved. We advise that you have a day with one of our Implementation Consultants on site to help you set up a branch system. However, this chapter should give you a good idea of what the Branches module can do for you. It is perfectly possible to convert an existing system to a Branch system, if you require. Call us for details.
What the user sees
In a Branch system, the User Account Details page has an extra tab called "Branches".
From this tab you can set the view permissions for the user. Options for which branches they are allowed to view are:
- All branches
- Individual Branches (tick/select every branch you want this user to be able to see)
- Groups of Branches (Views)