Permissions: who can see and do what
See which of your application's roles can see, add, change and delete each kind of record, and ask for a change to it.
The Permissions tab shows who can do what inside your application: for each kind of record, which of your application's roles can see it, add it, change it and delete it. You find it under What it is, on the Permissions tab.
These are the roles of your application's own users, such as a technician, an office manager or a customer booking online. They are not the people in your Divvent account, who build and approve the application. Those are on People: see People and roles.
Read the table
The table is headed Who may do what. Each row is a kind of record, such as jobs, invoices or customers. Each column is one of your application's roles. In each cell are four buttons:
| Button | Means the role can |
|---|---|
| Read | see records of this kind |
| Create | add new ones |
| Change | edit ones that exist |
| Delete | delete them |
A button that is switched on is highlighted. On a phone the table scrolls sideways inside itself.
Where a role can see or change only some records or some details, the cell says which, for example "only where the job is assigned to them". Where it can see or change everything, it says every record, every field.
Some buttons can't be pressed. Hover over one to see why. For example, a kind of record your application has exactly one of, such as your business's own details, can't be added or deleted by anyone.
Change who can see what
- Press Read, Create, Change or Delete in a cell to switch it on or off.
- To narrow what a role can see or change, open the line under the buttons (it starts Read: or Change:).
- Under Only these fields, tick the details the role may see or change, and press Set the fields. None ticked means every field.
- Under Only the rows where, write which records the role may reach, and press Set the rows. If you're not sure how to put it, ask for it in your own words on Changes instead: see Ask for a change.
- Each press goes into your draft straight away, and the screen shows What the change does below the table.
- When you are happy, press Ask for this change. It opens the change's own page, where you read it and approve it. See Read a change and approve it.
Start again throws the draft away. The same draft is shared with the Pages, Flows and Change the model tabs, so one change can include edits from each, and you ask for it once.
Owners, admins and editors can make changes here. Anyone else who can open the application can look.
Who approves it
A change to who can see what is a change like any other, and it is treated carefully:
- Taking access away is yours to approve, the same as any other change your account approves itself.
- Giving a role more is always approved by someone on our team, whatever your account can approve on its own. That means switching on a button that was off, or letting a role reach records or details it could not reach before.
The draft says which it is before you ask for it. On the change's page, the list of what changes always says who can see what, even when the answer is "unchanged".
Approving makes a new version. The new permissions apply once it is released: see Release a version.
What you can't change here
You can't add a new role or rename one on this tab. Ask for it in your own words on Changes. To check what a role actually sees on a page, use View as on the Pages tab: see Change your pages.