Grid82
grid82.comJoin the waitlist
UseRecords and comments

Records, comments, and history

Open any record in the record sheet to edit fields side by side, collaborate with threaded comments and mentions, and audit field history.

Expanding any record opens the Record sheet, a focused side drawer showing all fields you can read on that record alongside two collaborative panels: Comments and History.

Runtime record drawer showing Northwind Enterprise Renewal with Comments button (1) and History button (2) badged

A deal record open in the Runtime drawer with Comments (1) open and History (2) beside it
  1. Comments: Toggle the threaded comment stream attached to this record.
  2. History: Toggle the field-by-field audit trail showing who changed what and when.

Threaded comments and mentions

Use record comments to keep context on the deal, invoice, or ticket itself rather than losing decisions in external chat threads:

  • Type @ to mention any colleague who is a member of the app (comments.mentionable).
  • Comments travel with the record: if you delete a record and later revert the deletion from the change log, its comment thread returns intact.
  • Edit or delete your own comments inline inside the thread (comments.update, comments.delete).

Reading field history

Opening History (2) shows a chronological feed of changes made to this record:

  • Each entry names the actor (a user, an API key, an agent, or a workflow), the origin surface, and the exact before/after values.
  • Permission masking applies to history too: if your role hides a sensitive field, changes to that column never appear in your history stream.
  • Record creation, edits, comments, and deletes appear cleanly in sequence so anyone picking up a record can see why its status moved.

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.