Docs · Org admins
Who can see what
Access in Cue-Queue is decided by rules your owners and admins write, on the Access tab of the organization’s settings. Assistants follow the same rules as the people they work for.
The default
A new organization starts with one rule: everyone can read the team’s space. Nobody but owners and admins can change anything in it until a rule says so. Each person can change everything in their own space, unless a rule you write says otherwise.
A rule
A rule says who can do what in which part of the team’s space.
- Which part: a folder, a document or a list, and everything inside it.
/is the whole team’s space. A part can also be a pattern, such as/clients/*/contracts, and~means each person’s own space. - Who: one person, a group, or everyone with a role. Groups are made on the
Roles & Groups tab; the built-in
everyonegroup always holds every member. - What:
- read: see it.
- write: see it and change it: create, edit, move and delete.
- admin, beside read or write: also manage it, such as letting a page run as a dashboard or setting up a folder that follows a git repository.
- Or single actions on lists of work, such as adding items without being able to take them, for people who hand work in but should not process it.
- Nothing (no boxes ticked): not even see it. Use this to carve a private folder out of a shared part.
Order matters
Rules apply top to bottom, and where more than one reaches the same place, the last one decides. So write the broad rules first and the exceptions after them:
| # | Where | Who | What |
|---|---|---|---|
| 1 | / |
everyone | read |
| 2 | /sales |
group sales |
write |
| 3 | /sales/contracts |
everyone | nothing |
| 4 | /sales/contracts |
group legal |
write |
Here everyone reads the team’s space, the sales group can change the sales folder, and contracts are hidden from everyone except the legal group, the sales group included, because rule 3 comes after rule 2. (Owners and admins see everything whatever the rules say.) Move a rule up or down with the arrows beside it.
Checking
The simplest check is to ask, as the person concerned:
Which parts of the workspace can I change?