Grid82
grid82.comJoin the waitlist
Get startedUI quickstart

UI quickstart

Create a suite and app in the Studio, add a table and a role, publish a change, and open it as a user in the Runtime.

This walkthrough takes you through building a working Sales CRM app in the Studio and opening it in the Runtime as an invited user.

Open your suite in the Studio

Sign in to https://studio.grid82.app and open your suite. The suite page shows its Apps list (2) along with user directory and custom domain settings. Click an app such as Sales CRM (1) to open its builder workspace.

Studio suite overview showing Sales CRM (1) and Apps tab (2)

A suite in the Studio listing its apps (1) and the Apps navigation item (2)

Define tables and fields

Inside the app’s Data view, use the table tabs (1) to switch between tables such as Deals, Companies, and Contacts. Click + (3) on the right of the header row to add typed fields (currency, select options, links to another table, rollups, or formulas), and click New record (2) to add sample records.

Studio data grid showing Deals tab (1), New record button (2), and Add field button (3)

The Studio data editor: switch tables (1), add records (2), or create fields (3)

Set user roles and invite members

Open User roles in the app sidebar to define who can see which tables, records, and fields. For example, Sales Manager might see all deals, while Sales Rep sees only deals assigned to them. Then open Users to invite team members to the suite and assign their roles.

Read Roles and permissions for the full rule matrix.

Add an Interface page or an automation (optional)

Open Interface to build custom React pages using Grid82’s SDK and UI blocks, or open Automations to write TypeScript workflows triggered by record changes, schedules, or webhooks. Both work out of the box with the roles you defined.

Open the app in the Runtime

Click Open app in the Studio header (or navigate to https://{suite}.grid82.app/{app}) and sign in as one of your suite users. They land in the live app with the Data grid (1), published Interface views (2), pending approvals (3), and the built-in assistant (4).

Runtime app shell showing Data (1), Interface (2), to approve (3), and assistant (4)

The same Sales CRM app open in the Runtime for an invited team member

Where to go next

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.