Grid82
grid82.comJoin the waitlist
BuildInterfaces overview

Interfaces overview

How Grid82 Interface pages work, how sandboxed cross-origin execution isolates scripts, and how locked pages differ from templates.

Every app includes an Interface layer alongside its raw Data grid. Rather than drag-and-drop widgets limited to static layouts, each Grid82 page is a single TypeScript and React file compiled against the platform’s SDK and UI kit.

Security and permission model

Interface pages execute inside a sandboxed cross-origin iframe served from https://pages.grid82.app, completely separated from studio.grid82.app and your suite’s Runtime origin ({suite}.grid82.app or your custom domain):

  • No session cookies or raw network. Pages run without allow-same-origin, cannot read browser cookies or localStorage, and cannot issue arbitrary fetch or WebSocket calls.
  • Permission-filtered bridge. All record reads, SQL queries, file uploads, and mutations cross a typed message bridge back to the Runtime host, which executes every call through the active user’s role compiler.
  • No secret leakage. Never place API keys or third-party credentials in page code. Page source is browser code.

Page distribution modes

Builders set each page’s audience (visibleTo: a list of role IDs or "*" for all members) and distribution mode:

ModeBehaviour in RuntimeBest for
LockedUsers run the published version directly without editing its codeOfficial dashboards, client portals, approval consoles
TemplateShown under Templates in Runtime; roles allowed to build pages can fork an editable personal copyStarting kits that reps or operators tailor for their own workflow

visibleTo controls who sees a page in the navigation bar. It never grants table or field access: if a user opens a page referencing columns hidden from their roles, the page shows only their accessible records and respects their write restrictions.

Immutable versions and publishing

Saving a page compiles and bundles its TypeScript source immediately (returning exact SDK type errors before anything is stored) and writes a new immutable version number. Publishing simply moves the live pointer to a chosen built version:

  • Active users keep the version loaded in their tab until refresh.
  • Rolling back is an instant pointer update to a prior built version (pages.publish).
  • If a builder renames or deletes a field that a page depends on, Grid82 displays a structured repair banner rather than a blank crash.

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.