Give everyone exactly the access they need
Role-based access control (RBAC) with a permission matrix, record scope (own, team or all), field-level permissions, scoped API keys and a tamper-evident audit log. Set it up by clicking, without code.
For admins, IT and security reviewers who need to know who can see and change what.
Why it matters
One workspace for the whole company only works if access is precise.
Protect sensitive data
Salaries, margins and private notes stay with the people who need them, even inside a shared app.
Let people work on their own
Give each team a workspace that shows their records and hides the rest, without building separate apps.
Answer “who changed this?”
Every sign-in and every change to a record is recorded, with the values before and after.
How it works
Three layers: what a role can do, which records, and which fields.
- 1
Create roles
A role is a set of permissions, such as Sales rep or Finance. For each module and action, choose None, Own, Team or All.
- 2
Fine-tune fields
For sensitive entities, mark fields as Read only or Hidden for a role. Everything else stays Read & write.
- 3
Assign people and teams
Give users one or more roles and put them in teams. Their effective permissions are shown on their profile.
Try it: see a record through a role's eyes
Switch roles to see which deals each one can open, and which fields it can edit.
View the Deals app as
Field permissions on one deal
Deal name
Northwind renewal
Stage
Negotiation
Amount
$48,000
Discount
12%
Margin
••••••
Internal notes
••••••
Sample data. Record scope and field permissions are both set per role, entity by entity.
See it in a real business
A short walkthrough that follows one business through the problem and the fix.
Security & control 2:37
Permissions and approvals: who sees what, who signs off
Harbor Supplies, selling to 400 restaurants
Every week the same question caused an argument: who is allowed to give a discount? This is how they settled it.
- Roles with None, All, Own and Team access
- Hidden fields that are never sent to the screen
- A two-step approval with a deadline, expiry and reassignment
- An audit log you can verify
Chapters (11)· jump straight to a part
More to watch
Security controls
The controls a security review usually asks about.
Permission matrix
For each module and action (create, read, update, delete and more), set None, Own, Team or All. Bulk-set a whole module in one click.
Teams
Group users into teams. Team scope lets managers see and work on everything their team owns.
Field-level permissions
Make any field Read & write, Read only or Hidden for a role, entity by entity.
Sign-in security
Two-factor authentication with an authenticator app and backup codes, Google sign-in, email invitations for new users, and throttling of repeated failed logins.
Audit log
Filter by date, action, user or record type, expand an entry to see before and after values, and export to CSV or JSON. Entries are hash-chained, so tampering is detectable.
Scoped API keys
Limit a key to specific permissions (for example, read entity data and reports only) and set it to expire in 30 days, 90 days or a year. Keys are shown once.
Offboarding
When someone leaves, transfer the records they own to a colleague and disable their account in one step.
Quick changes in plain words
Type “Read only for Finance” or “Revoke all HR permissions” in the role editor to apply a change, then review it in the matrix.
Separation of duties
By default, the person who triggers an approval request can’t approve it themselves.
Frequently asked questions
Straight answers for buyers and security reviewers.
What do Own, Team and All mean?
They set which records a role can act on. Own means records the user owns (the entity's owner field, such as “Assigned to”). Team means records owned by anyone on the user's teams. All means every record in the workspace. You can choose a different scope for each action, for example read Team but delete Own.
Can I hide individual fields from some roles?
Yes. In the role editor, each field of each entity can be Read & write, Read only or Hidden for that role. A typical setup lets sales reps see a deal but not its margin.
Do you support single sign-on (SSO) and SCIM provisioning?
Yes. Workspace admins can connect an identity provider with SAML 2.0 or OpenID Connect, verify your email domains, require SSO sign-in and create accounts automatically on first login. SCIM 2.0 keeps users and groups in step with your directory. Without SSO, users sign in with email and password, optionally with two-factor authentication, or with Google.
How long is the audit history kept?
Audit history depends on your plan: 30 days on Starter, 365 days on Pro and custom on Enterprise. You can export the log to CSV or JSON at any time.
Can you help with security reviews and compliance questions?
Yes. The Enterprise plan includes compliance support, such as data residency options and help with security questionnaires. Contact us to discuss what your review needs.
Related features
Scratchboard features that work together with this one.
Workflows
Approvals with roles, teams and deadlines.
Entity engine
The records and fields permissions apply to.
AI Builder
Generates roles along with your app.
Integrations
Scoped API keys and signed webhooks.
Reports
Private, team or company-wide sharing.
Developers
Authenticate to the REST API with API keys.
Use cases
Access setups for HR, finance and sales.
Pricing
Roles and audit history per plan. Every plan starts with a 7-day free trial.
Set up access the right way from day one
Every plan starts with a 7-day free trial. The AI Builder creates starter roles with your app, and you can refine them in minutes.