Permissions are the abilities that members of a space have to work with its files.
Permissions are granted to members by managers of a space.
Permissions can be grouped into roles. For more, see Create custom roles in a space.
Step-by-step:
1. Select the space you want to manage.
2. Click Manage → This Space in the right-hand sidebar. The Manage Space modal will open at the People tab.
3. Go to the Members carousel.
4. Click once on permission symbols to disable or enable View, Download, and Edit permissions. This will enable or disable these permissions for all members.
5. Click the ellipsis (...) above the Members row to reveal a full list of Custom Permissions.
6. Apply a check or cross to each permission, or leave the permission box blank:
| Permission Checkboxes Explained | |
|---|---|
| Check | Enable this permission for members. |
| Cross | Disable this permission for members. |
| Blank | Chorus allows users to be in more than one role in the same Space. Where a box is left blank, the permission is disabled unless another role enables it. For further details, see the end of this page of documentation for examples. |
7. Click Save.
Advanced Usage: Details on how Permissions Checkboxes interact with roles
Users can be in more than one role in a Space. The "blank" permission (unchecked) has particular behaviour in this situation, which should normally provide a convenient solution that does what's most logical for your users.
For each permission, e.g. 'download', Chorus checks the roles for the user in question. It checks the roles in this order:
1: Managers role,
2: Custom roles,
3: Members role
In the order defined above, Chorus checks the permissions checkboxes:
- If any of them have a cross, then the user does not have that permission (Chorus stops checking here);
- If any of them have a tick, then the user does have that permission (Chorus stops checking here);
- If all of them are blank, we carry on to the next group of roles.
If none of the groups of roles resolve a permission for the user, then the user does not have that permission.
Example: A user is in Managers & Members:
- Managers has download blank and Members has download ticked, then the user does get the download permission.
- Managers has download ticked and Members has download crossed, then the user does get the download permission.
- Managers has download crossed and Members has download ticked, then the user does not get the download permission.
- Managers has download blank and Members has download blank, then the user does not get the download permission.
Example: A user is in two custom roles, 'Role A' and 'Role B':
- Role A has download blank and Role B has download ticked, then the user does get the download permission.
- Role A has download ticked and Role B has download crossed, then the user does not get the download permission.
- Role A has download blank and Role B has download blank, then the user does not get the download permission.
More on managing users in spaces:
You are here:
