Permissions
The individual things a person is allowed to do, like view, edit, or delete a particular item.
Editor
- View ✓
- Edit ✓
- Delete ✗
Viewer
- View ✓
- Edit ✗
- Delete ✗
What it is
Permissions are specific abilities: can view, can comment, can edit, can delete, can invite. They can apply app-wide (through roles) or to a single item (sharing one document with one person).
Per-item permissions, like Google Docs sharing, are powerful but much more complex to build than a few app-wide roles. Ask for them only if you really need them.
It helps to write a small table: rows are actions, columns are roles, and each cell says yes or no.
How to ask for it
“Some people should be able to edit and some just look.”
“Each project has per-project permissions: the owner can invite people as Editor (can edit tasks) or Viewer (read-only). Viewers don't see edit buttons, and the backend rejects their edits.”
"Some edit, some look" doesn't say whether it's app-wide or per project; naming per-project permissions and the levels defines the model.
You've seen this in
- SSharing a Google Doc as "Can comment"
- DFolder access in Dropbox
- SChannel posting permissions in Slack