|
|
| (72 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| − | {{template:admincomingsoon}}
| + | #REDIRECT [[Users]] |
| − | | |
| − | __TOC__
| |
| − | | |
| − | Since Charitylog is based online, and the whole organisation has access to the information stored on it, it is important that user access is well controlled.
| |
| − | | |
| − | We suggest that it is a good idea to be as lenient with access as possible, and to trust staff as much as possible. If you try to tightly control every single user with a set of complicated rules about what they can and can't see, it is likely to lead to an awful lot of extra work for administrators.
| |
| − | | |
| − | There are three ways to limit user access within Charitylog.
| |
| − | | |
| − | ==Limiting access for particular users==
| |
| − | | |
| − | ===System Access tab===
| |
| − | | |
| − | ===Project Access tab===
| |
| − | | |
| − | ===Personal Tab Access tab===
| |
| − | | |
| − | ==Limiting access by user group==
| |
| − | | |
| − | ===Group Access screen===
| |
| − | | |
| − | The Group Access screen allows administrators to control what each [[User Groups|User Group]] has access to throughout the Charitylog system. It is one of the most powerful tools that administrators have in running the system, and is covered in its own document here: [[Group Access]].
| |
| − | | |
| − | ==Limiting access to a specific document, etc==
| |
| − | | |
| − | ===Uploaded documents===
| |
| − | | |
| − | ===Extension Databases===
| |
