Role-based access control in Rig: control who can access what data
Fine-grained access controls let you decide exactly who in your team is allowed to see, edit, or request which data, all the way down to the row and column.
Access gateway: who sees which schema
Inside the access gateway, every data collection and schema you've connected to Rig shows up in one place. The schema matrix is where you decide who is allowed to access what.
| Schema | owner | editor | analyst | viewer | sales |
|---|---|---|---|---|---|
| CRMmedium4/5 | |||||
| Meeting noteslow5/5 | |||||
| Banking (payroll)high3/5 | |||||
| Product analyticslow4/5 | |||||
| Banking (ops)critical1/5 | |||||
| Warehousemedium3/5 |
PII, financial data, and context-layer permissions
Beyond schema access, you can decide who can edit data context and what sensitive categories each role is allowed to see. Rig auto-classifies PII, financial, and confidential fields when it builds your context layer, and you can edit the classifications whenever you need to.
| Role | PII | Financial | Confidential |
|---|---|---|---|
| owner | allow | allow | allow |
| editor | partial | allow | redact |
| analyst | hash | allow | null |
| viewer | null | null | null |
Column masks, row filters, and area grants
Mix and match four primitives to model how each role sees your data, with column-level masks and row-level filters that scope exactly which cells and which rows a role can read.
Column mask
Redact specific columns for a role.
Row filter
Limit which rows a role can see.
Table override
Allow or block a specific table.
Area grant
Permit a virtual collection of tables.
Test a role before you assign it
Under Test access in the Access settings, pick a role and see what it can reach. What can <role> see? lists every table and VDM the role can read, with its masked columns, next to the ones it is blocked from, and you can run a SQL query as the role to see exactly what comes back. Owners can also test as a person, which applies that person's row scope too. Confirm the masked columns and filtered rows match your policy before you grant the role to anyone.
Pick a role
Owner · Editor · Analyst · Viewer, or a custom role
Check what it can see
Tables and VDMs split into readable and blocked.
Run SQL as the role
Click a readable table or insert a template query.
Inspect
See which columns come back masked and which rows are filtered out.
Model permissions so that anyone on the team can plug into your internal data and context layer from Claude or Cursor, while the data team sets permissions on who is allowed to access what and tests that they work.