Grid82
grid82.comJoin the waitlist
User rolesReplace one role's permissions

Replace one role's permissions

Set permissions for this role only; other roles remain untouched, and permissions never cross between roles or require ordering.

PUT/v1/apps/{appId}/roles/{roleId}/permissions

Include every table the role should access; omitted tables become inaccessible. tables is "*" (everything, future tables included) or a map of table id to grant. Example, read all rows, edit only stage, hide every other field: {"tables":{"tbl_deals":{"access":"granted","fields":{"mode":"selected","entries":{"fld_name":{"see":true},"fld_stage":{"see":true,"edit":true}}},"update":"all"}}}. A field absent from entries is hidden; fields: {"mode":"all","edit":"none"} shows every field, future ones included. rows, update and delete take a filter group as views do, to limit rows. Simulate first if unsure who is affected. Send the revision from roles.get as baseRevision; if someone changed this role after that revision, the save is refused with 409 instead of erasing their change.

Requires the schema:write scope. Operation roles.setPermissions. MCP tool roles_setPermissions. CLI: grid82 roles set-permissions (npx grid82).

Path parameters

NameTypeRequiredDescription
appIdstringyes
roleIdstringyes

Headers

NameTypeRequiredDescription
Idempotency-KeystringnoAny unique string. Sending the same key with the same request again returns the first response (marked Idempotency-Replayed: true) instead of running it twice. Reusing it for a different request is refused with 409. Kept for 24 hours. Up to 255 characters.

Request body

FieldTypeRequiredDescription
tables”*” or objectyes
baseRevisionstringno

Response

application/json

Success

dataobjectrequired

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.