Grid82
grid82.comJoin the waitlist
BuildRoles and permissions

Roles and permissions

Define user roles per app, control tables, records, fields, and actions, understand the additive union rule, and simulate access before saving.

Every read and write in an app passes through the same compiled permission matrix, whether it comes from the Runtime grid, an Interface page, the REST API, the CLI, or an MCP agent. There is no special Runtime admin mode and no credential that skips these rules.

Studio roles permission matrix highlighting Sales Rep role (1) and Edit permissions button

Editing Sales Rep table, record, and field permissions in the Studio role matrix

In the Studio, select any role on the left (1) such as Sales Rep, then click Edit permissions (highlighted in red) to configure what that role can access.

Four independent layers

Permissions are configured per role across four narrowing levels:

  1. Table access (access): "granted" or "none". If "none", the table is absent from the user’s UI, API schema, OpenAPI document, and MCP tools.
  2. Record filter (rows): Optional filter tree restricting which records are visible (for example, Owner is @me). Without a filter, the role sees every record in the table.
  3. Field access (fields): Either "all" (with edit: "all" | "none"), which automatically includes future columns added to the table, or "selected", which explicitly lists allowed fields (see and edit booleans per field). Use "selected" whenever a role must not automatically see newly added columns.
  4. Action verbs (create, update, delete): Boolean create, plus "none", "all", or a narrowing filter for update and delete.

A role can also hold wildcard full rights ("*") inside that app if it represents internal operators who need unrestricted schema visibility.

Why roles only add access (union rule)

A user can hold multiple roles simultaneously. Grid82 computes their effective access as the union of their roles, evaluated per table, per record predicate, per field, and per operation:

  • There is no explicit deny and no priority order between roles. Adding a role can only grant equal or more access.
  • Seeing is always the gate: a user cannot edit a record they cannot read, and cannot write a field they cannot see.
  • Record-conditioned fields. If a user can read a sensitive field (like Margin) only on a subset of records (Stage is Won), filtering or sorting by that field is blocked (403) so nobody can infer values on records outside their scope.

Simulating permissions before publishing

When combining multiple roles or editing complex record conditions, open Users, choose See their permissions, or run rules.simulate in the Builder API or MCP:

Terminal
grid82 rules simulate app_5mg8rw2kx4tn \
  --roles rol_salesrep123 \
  --table-id tbl_8fj3kq2wmv5d \
  --op read

rules.simulate runs the exact production permission compiler without altering any grants and explains which role contributed each capability.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Grid82 documentation and read it in full, instead of answering from memory.

https://grid82.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://grid82.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.