Grid82
grid82.comJoin the waitlist
BuildTables and records

Tables and records

Design tables, columns, and relational links in the Studio grid, inspect schema impact before destructive changes, and recover from trash.

In the Studio, every app opens directly to its Data workbench. Tables hold your records, and fields define the types, links, and calculations stored on each record.

Studio grid view highlighting table tabs (1), New record button (2), and Add field button (3)

The Studio data editor for Sales CRM showing table tabs (1), New record (2), and the add-field trigger (3)
  1. Table tabs: Switch between tables in the current app (Deals, Companies, Contacts) or create a new table.
  2. New record: Add records directly in the grid, or import records via the API, CLI, or Studio assistant.
  3. Add field (+): Append a typed column, relation, lookup, rollup, or formula.

Managing tables safely

Every table has a permanent ID (tbl_...), a display name, and an optional icon. When designing a multi-table model (for instance Companies, Contacts, and Deals), create related tables together or link them with link fields.

  • No shared builder views in Studio. Builders can filter and arrange columns locally while inspecting data in the Studio, while saved personal views live in the Runtime for app users. To create a permanent screen for your team, build an Interface page.
  • Primary field. Keep the first column descriptive (such as deal title or company name). Linked record chips across the app and in the API ([{ id, label }]) display the target record’s primary field automatically.

Schema changes and impact checks

Adding a new table or field is immediate and safe. Before renaming or deleting an existing column, inspect its impact:

  • Impact check. Grid82 traces which permission rules, formulas, lookups, rollups, workflows, Interface pages, and user views depend on a table or field (schema.impact in the Builder API).
  • Type conversions. Changing a column’s type converts existing cells inside a single transaction; incompatible values are cleared rather than guessed. To keep old values safe while migrating, add a new column first.
  • 30-day trash. Deleting a table or field moves it and its data to the app’s trash for 30 days. Restoring from trash (trash.restore) brings back the original IDs, values, links, and role references.

Bulk imports and scripts

You can seed records directly in the grid, run grid82 records create from the CLI (up to 500 records per batch), use sql.execute for conditional updates (UPDATE ... WHERE), or drop a CSV/XLSX file into the Studio assistant.

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.