Grid82
grid82.comJoin the waitlist
BuildTeam and users

Team and app users

Manage Studio builders and suite end users, send invites or share join links, assign app roles, and inspect effective user permissions.

Grid82 distinguishes Studio builders (team members who configure schemas, permissions, pages, and billing inside an organisation) from App users (end users who sign in to one suite’s Runtime apps).

Studio builders vs App users

BuildersApp users
Where managedOrganisation -> TeamSuite -> Users and App -> Users
Where they sign inhttps://studio.grid82.apphttps://{suite}.grid82.app (or suite domain)
RolesOrganisation roles (admin, member)Per-app user roles (Sales Manager, Client, etc.)
Billing quotaCounted under Studio buildersCounted once per email across all suites in the organisation

Inviting and assigning app users

You can onboard people into a suite in three ways:

  1. Direct email invite (users.invite): Add a person by email and assign initial roles on specific apps. Pending invitations reserve one app user seat until accepted or revoked.
  2. Suite join links: Enable or share an invite link so colleagues can self-register into the suite with a default onboarding flow.
  3. Directory management (members.add / members.update): Grant an existing suite user access to another app in the same suite, update their role list, or suspend access immediately.

If an invited user loses access to their inbox or needs a fresh sign-in link, builders can generate a one-time password link from the user menu (users.passwordLink).

Inspecting effective permissions

Because a user can hold several roles at once, the fastest way to verify what an individual actually sees is inside the app’s Users list. Open the action menu (...) beside any user and select See their permissions.

Studio user access inspection dialog for clara.moreau@meridian.test

Inspecting a user's compiled permissions across tables and roles in the Studio

The inspection dialog displays the user’s combined access table by table (which columns are visible, which are editable, and any record filter), computed by the exact same compiler that enforces live requests.

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.