Branches

From Charitylog Manual
Revision as of 13:32, 7 August 2015 by Rob Kay (talk | contribs) (Created page with "right In standard form, Charitylog allows our customers to share details of all of the organisations/people they deal with across all of their s...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Helpheader small.png

In standard form, Charitylog allows our customers to share details of all of the organisations/people they deal with across all of their staff. Work done with those people can be hidden 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 some 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. They 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.