---
title: "Interfaces overview"
description: "How Grid82 Interface pages work, how sandboxed cross-origin execution isolates scripts, and how locked pages differ from templates."
canonical: "https://grid82.com/docs/build/interface-overview"
updated: "2026-11-20"
---

# Interfaces overview

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:

| Mode         | Behaviour in Runtime                                                                                  | Best for                                                           |
| ------------ | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
| **Locked**   | Users run the published version directly without editing its code                                     | Official dashboards, client portals, approval consoles             |
| **Template** | Shown under **Templates** in Runtime; roles allowed to build pages can fork an editable personal copy | Starting 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.
