---
title: "Introducing the Dash: the mind seen from above"
summary: "A member-only control panel assembled from small UI kit pages, with the host retaining authority over every connection."
created: "2026-11-15"
updated: "2026-11-15"
revision: "1"
previous: ""
reviewedThrough: "b0b2ed37708d39699ee3007262c65b822b04790b"
sourceDigest: "46cc2bf98845b5185e694ab15f47c2199949f2eaf25e86040fb4af295835828c"
---

With this, your mind can show its members where work, repos, integrations and access controls live without inventing a dashboard framework. The Dash is a page in the mind’s own config, so changing its navigation is an ordinary code change. It is not a new public API for the information it displays.

## One list defines the page

`apps/dash/public/app.js` imports `Dash` and its overview, contexts, repo, integrations, analytics and other panels from `@iterate-com/ui`. A `pages` list supplies their names, icons, order and components. The sidebar and overview cards come from that same list, so they cannot disagree. `?page=<id>` names the selected panel. Larger panels load when needed rather than burdening the overview.

```js
const pages = [
  { id: "overview", name: "Overview", component: Overview },
  { id: "notes", name: "Notes", component: Notes }
];
// Each component receives the member itx and page context.
```

`apps/dash/app.ts` serves `index.html`, `public/` and the shared theme. After `this.auth.require(request)` in `worker.ts`, `host.auth.memberPage(request)` handles the member socket and shell endpoints. The browser uses `memberItx()` and `mindOfHost()` from the UI kit. Do not expose this socket behind the weaker signed-in-person guard: a member can inspect the whole mind.

## Integrations belong to their real owner

The Integrations panel renders what the mind’s integrations facet and secret inventory say, rather than keeping a second list in browser storage. A guarded `/connect/<app>` route begins an OAuth flow through the configured iterate Cloud, using scopes from `cloud-scopes.ts`. The vault shows the member the proposed secret and destinations before consent. Connecting again can replace only a secret of that same app; it cannot overwrite an arbitrary secret named by a link. No credential passes through the page’s JavaScript.

## Building your own

Use a small host function with the member guard, pin the UI kit in the import map, define a page list, and delegate authorization to the platform. Store durable state through the mind’s existing facets rather than adding local browser authority. The basic dashboard needs no new secret. Individual panels naturally need whatever integrations they show, and OAuth connection buttons need a configured Cloud client. Existing secret and membership management remain platform pages, not copied forms. Test signed-out and nonmember refusals, direct requests to the socket, unknown panel ids and a disconnected session. [Agents](/introducing/agents), [Docs](/introducing/docs) and [Mail](/introducing/mail) are separate member apps reached from this wider control plane.
