Roles and permissions: who sees what
Updated
Every person in a base has a role, and the base's owners can narrow it: who may add, change and delete records, who sees each table, and which records of a table each person sees. Artavolo checks these rules on the server for every request, so they hold in the base's screen, the API, AI chat, AI agents, attached files, the trash and live updates alike.
The roles
| Role | What they may do |
|---|---|
| Owner | Everything, always: every table and record, sharing, settings, automations, forms, files, insights and the permissions below. |
| Contributor | By default adds, changes and deletes records, comments and writes notes. |
| Read only | Sees the tables and records allowed to them and opens interfaces. Changes nothing. |
| Guest | Views a base opened with Guest Access, without an account: only the tables set to be seen by guests. |
People in a workspace have their workspace role in each of its bases. People invited to an interface alone are Editor, Commenter or Read only there, and see nothing else of the base: see Build an interface.
Set who may do what
- Press Share and choose Base / Group.
- Scroll down to Permissions.
- Under Records, answer Who can change records?, Who can add records? and Who can delete records? with Contributors and owners, Owners only, Specific people or Nobody. For specific people, pick them.
- Under Tables, choose Who sees it for each table: Everyone with access, guests too, Members, read-only and up, Contributors and owners or Owners only.
- Press Save.
Who may add records is never wider than who may change them: the panel offers only what fits, and the server refuses anything else. Back to the defaults returns to contributors adding, changing and deleting records and everyone with access seeing every table and record.
Show people only their own records
In the same table list, Which records they see sets a rule for each table:
- Choose Only where a field: Created by (who added the record), a person field, or a text field such as an e-mail address.
- Choose is them, to show each person the records that name them, or is and a value, to show only records with that value.
- Choose whether it applies for everyone but owners or for read-only members only.
- Press Save.
A salesperson then sees their own deals, or a client the requests that carry their e-mail address. A person's new records are filled in to match the rule, only an owner can change the field the rule is about, and a restricted person cannot empty the table.
Good to know
- Only owners see and change the permissions. Owners always see every record, as do the administrators of a self-hosted installation.
- Commenting on a record needs the right to change records in its table, so read-only members read comments but do not add them.
- An API token acts as the person it belongs to, with the same rules. AI agents are members with a role of their own and are held to the same rules.
- Guests are nobody in particular, so an is them rule shows them nothing.
- Someone limited by a rule sees changes made by others when they next open the table, not live.
- A field's own settings have Who can edit its values, which shows the field read-only on the table screen to everyone not chosen.
- Every change to the permissions is kept in the audit log, with what it was.