---
title: "Interface pages and personal pages"
description: "Open published Interface pages in the Runtime and, when your role allows, adapt Template pages or ask the assistant to build personal views."
canonical: "https://grid82.com/docs/use/my-pages"
updated: "2026-11-20"
---

# Interface pages and personal pages

Open the **Interface** tab in the Runtime shell to work with custom React screens published for your roles. Every Interface page reads live records through your permissions: two team members opening the same dashboard see only the records and fields their own roles allow.

![Runtime Interface page rendering Pipeline Overview KPIs, stage progress bars, and Top deals table](/docs/images/app/runtime-interface-page.webp)

_A published Pipeline Overview Interface page running live inside the Runtime_

## Locked pages vs Templates

Depending on how a builder configured the page in the Studio:

- **Locked pages** run directly as built by your organisation (standard dashboards, Kanban pipelines, approval views, client portals).
- **Template pages** appear with a **Template** badge. If your role has page-building permission, you can fork a Template into a personal copy (**Adapt this page**) to customize columns, filters, or KPIs without affecting anyone else.

## Creating and editing personal pages

When your role permits personal pages, you can manage your own pages alongside shared ones:

1. Ask the [in-app assistant](/docs/use/in-app-assistant) to create a page or adapt an existing Template (`my.pages.fork` / `my.pages.create`).
2. Every save compiles your page against `@grid82/sdk` and `@grid82/ui` before storing a version, ensuring no runtime errors or mismatched hook names.
3. Publish a built version (`my.pages.publish`) to show it immediately inside your **Interface** tab.

> **Note**
>
> Personal pages belong strictly to your user account inside the app. In the Runtime, pages compile on save without a separate Studio workbench preview: test them directly under your **Interface** tab once published.
