---
"@type": Article
"@id": "https://helloloam.dev/principles/no-dashboards"
"@source": "https://helloloam.dev/data/article/no-dashboards.json"
"@stamp": "2026-10-22T21:53:55+00:00"
about:
  "@type": DefinedTerm
  "@id": "https://helloloam.dev/data/definedterm/no-dashboards.json"
  name: No dashboards to learn
  identifier: no-dashboards
  inDefinedTermSet:
    "@type": DefinedTermSet
    "@id": "https://helloloam.dev/data/definedtermset/gives-you.json"
    name: Gives you
    identifier: gives-you
author: {"@id":"https://helloloam.dev/#organization"}
datePublished: "2026-10-03"
description: A loam site has no admin panel — not a minimal one, not a hidden one. Your agent is the interface, and it works on the files directly.
headline: No dashboards to learn
identifier: no-dashboards
inLanguage: en
publisher: {"@id":"https://helloloam.dev/#organization"}
url: "https://helloloam.dev/principles/no-dashboards"
---

# No dashboards to learn

## The panel, and what it costs

An admin panel is the defining feature of a content management system, and its largest liability: a second application in front of the content, with [a login to attack](/principles/security-bolted-in), sessions to steal, forms that must mirror every field, and its own idea of the content that drifts from the templates. Loam removed it — not a minimal one, not a hidden one: none.

## Your agent is the interface

What remains is the files, the rules for how they may change, and one gate through which changes arrive: the MCP, [a protocol any assistant speaks](/byoa). You connect your site once, from the assistant you already use. `/admin` on your domain holds no login form but an explanation written for agents: what this site is, how to connect, what the rules are. To set up a new assistant, you hand it that address.

## Management in your own words

“Move the summer closure notice above the opening hours and make it less formal” is not a feature a panel offers. An agent works from what you mean: it finds the right file, makes the change and [stages it as a draft](/principles/draft-and-live-lifecycle) for you to preview and publish. “Add an English version of the about page.” “Take the old vacancies page offline.” “What changed last week?” There is no editor to learn.

## One truth

Your agent reads the same files the site renders. It does not guess where a title or a price lives, and no admin-side model can disagree with the page.

## The panel's other jobs, as data

| Panel job | Loam answer |
| --- | --- |
| **Explain the site** | `/admin`, readable by any agent |
| **List drafts, report refusals** | the MCP, in plain language |
| **Activity log** | the journal |
| **Map of the site** | the machine views |

Panels need training and documentation, and go out of fashion. A conversation does not.

## What it costs

A dependency on a capable assistant. Someone who may not or cannot use one needs another way in. Loam's answer is a principle — new kinds of users get new clients, never new doors — and that client exists: the edit client on `/edit`, off by default, speaking to the same MCP under the same rules. A client, not a panel, and never a second entrance with its own login.