Overview
Eight groups, forty-four screens, its own door, and the habits that make it quick to use.
/admin is where the installation is configured. It has its own sign-in at /admin-login, so the panel is a
separate door rather than the product with more buttons, and every change made inside it is written to an audit
log with the name of the person who made it.
The eight groups
Prop
Type
Each screen lives at /admin/ plus its own name, so Money → Plans & pricing is /admin/plans. A screen
that does not exist returns the not-found page rather than an empty panel, and the sidebar marks the group you
are in.
The four habits that make it quick
Save is explicit, and sometimes it is not
Most screens save as you change them and say so with a small confirmation. Three kinds of screen keep a draft instead, and the change lands when you press Save:
- anything with an ordered list that you are rearranging, such as the landing bands or the plans;
- notices, where a removal is staged until saved;
- the screens with destructive actions, where the button is the confirmation.
If a change does not seem to have taken effect, the first thing to check is whether the screen has a Save button you have not pressed.
Some actions ask you to type a word
Deleting a user, restoring a snapshot and clearing tables all ask for a typed confirmation. That is not theatre: those are the actions in this panel that lose something, and a typed word is the only kind of confirmation that survives a tired click.
Caps are shown before you reach them
Places with a limit, such as notices, webhooks, API keys and refused words in image prompts, show how many are used and how many are left. A limit that is reached disables the control that would exceed it rather than failing after the fact.
Anything unavailable says why
A card whose feature is not configured is disabled with the reason beside it, rather than offering a button that fails when pressed. That is the same habit as the sign-in screen saying a provider is not configured: the panel would rather admit a fact than perform a failure.
What the panel can and cannot do
Where to start, depending on what you are doing
| I am... | Start at | Then |
|---|---|---|
| Setting the installation up | Brand → Branding | Intelligence → Providers & keys, then System → Security |
| Launching publicly | System → Security | Money → Plans & pricing, Content → Legal pages |
| Trying to understand the numbers | Insight → Overview | Insight → Analytics for trends, Money → Credits for spend |
| Answering a support question | People → Users | People → Support for the message, System → Audit log for what changed |
| Fixing something that is broken | System → Status & health | System → Audit log, then Platform → Environment |
| Changing how the product feels | Brand → Appearance | Brand → Landing page for the words a visitor reads |
The audit log is the answer to most arguments
Every settings change is recorded with who made it, when, and which fields
moved. System → Audit log can be searched and exported as CSV, which is what
turns "it changed on its own" into a name and a timestamp.