In short
Record permissions decide who may read, create, change, delete and export each kind of record. The approach that holds up is to give permissions to roles, not to people, and to set them for each kind of record: the people who may read suppliers need not be the people who may change them, and neither group needs the payroll records. A spreadsheet cannot do this, because whoever has the file sees every row. Start with the least access each role needs, give API keys and automations a role too, and decide up front how you will handle the harder cases, such as showing one person only some rows of one kind of record.
Four levels of control, and where each fits
Access to business data can be controlled at four levels. They differ in how fine the control is and how much work it takes to keep correct.
| Level | What it controls | Example | Effort |
|---|---|---|---|
| The whole workspace | Who can open it at all | Only staff, not suppliers | Low |
| A kind of record | What a role may do with all records of one kind | Finance can change invoices; sales can only read them | Medium |
| A field | Which columns a role sees | Hide the salary column from most people | High |
| A row | Which records a person sees | A manager sees only their own region | Highest |
Roles, kinds of record and what each role may do
Why roles, not people
- People change jobs
- A rule written for a person has to be found and edited when that person moves. A rule written for a role follows the job.
- Review is possible
- A short list of roles can be reviewed. A list of individual exceptions cannot.
- Machines are included
- An API key or an automation that reads and writes records should hold a role too, so the same rules apply to every way data leaves or enters.
- Least access first
- Start every role with the least it needs and add. Taking access away later is the step people avoid.
The old way and the new way
The table compares how access works for a list kept in a spreadsheet with records that have permissions.
- Who sees what
- The old way: Whoever has the file sees all of it
- The new way: Each kind of record has its own permissions by role
- Showing an auditor
- The old way: Send the whole log, or build a cut-down copy by hand
- The new way: Give the auditor a role that reads the records they need
- A person leaves or moves
- The old way: Hope the old copies are deleted
- The new way: Change their role; the access follows
- An integration
- The old way: A shared login or a file drop
- The new way: An API key with a role, subject to the same rules
- Exporting
- The old way: Anyone with the file can copy it
- The new way: Export is an action a role may or may not hold
The harder cases to plan for
Two requests come up soon after the first set of permissions is in place, and they are worth planning for before you choose a tool.
- Hiding one field
- A salary or a price that most people should not see. A tool that only controls whole kinds of record cannot do this; the workaround is to keep the sensitive values in a separate kind of record with its own permissions.
- Showing only some rows
- A regional manager who should see only their region. Check whether the tool supports row-level rules. If it does not, the same workaround applies: split by kind of record, or by workspace.
- Exceptions
- Every organisation has one. Record each exception with the reason, and review the list on a schedule.
How we decided
In SynaptaGrid Data an administrator decides, for each role, who may read, create, update, delete and export each kind of record. API keys and automations are governed by the same grants: an API key gets a role, not a separate list of scopes. We agreed on that so that every route that data takes in or out gets the same answer.
We chose to start at the kind of record. Control of a single field or of single rows was a later step in our plan and is not something we describe here. The cost is that the harder cases above need the workaround of splitting data into separate kinds of record. The benefit is that the first level is simple enough for an administrator to review.
We checked this with test accounts in our own workspace: a reader role and an owner role, each tested for what it could and could not do.
Standards and accepted practice behind this
These are the practices the guide rests on. We align with them. This page does not claim a certification.
- Role-based access control
- Permissions are granted to roles, and people are assigned roles. It is the common model for business software.
- Source: NIST: role-based access control (opens in a new tab)
- Least privilege
- Each role gets the access its work needs and no more.
- Source: NIST glossary: least privilege (opens in a new tab)
- Separation of duties
- The role that raises a record is not always the role that approves or exports it.
- Source: NIST glossary: separation of duty (opens in a new tab)
- Periodic access review
- Roles and exceptions are reviewed on a schedule, because access drifts.
Where SynaptaGrid fits
SynaptaGrid Data sets permissions for each kind of record by role. A person who can read the suppliers need not be able to change them.
This guide does not claim that it can hide a single field from a role or show a person only some rows of one kind of record. If you need either, plan the split into separate kinds of record described above and ask us to confirm the current state.
Frequently asked questions
- What is record-level permission?
- It is control over who can read, change, delete or export data, set for each kind of record or even each record. The finer the level, the more work it takes to keep correct.
- What is role-based access control for business records?
- It is a model where permissions are granted to roles, such as Finance manager, and people are assigned roles. When a person changes jobs, you change their role and their access follows.
- Can an API key have permissions?
- It should. Giving an API key a role means the same rules apply to a machine reading and writing records as to a person.
- How do I show an auditor only some records?
- Give the auditor a role that can read the kinds of record they need and nothing else. If you need to show only some rows of one kind, check whether your tool supports row-level rules, or split the data.
SynaptaGrid
See permissions on your own records
Walk through the roles you would need and see what each one can do.