How Settings is laid out
One long scrolling record of nine chapters, every row numbered, every row editable in place. This is where the rest of the app takes its cues.
Updated Aug 14, 20262 min readApplies to 1.1.5
Settings isn't a set of tabs. Settings is a single document called the Ledger, running top to bottom in nine chapters:
| # | Chapter | Eyebrow |
|---|---|---|
| 01 | Account | HEALTH AND PLAN |
| 02 | The Voice | WHAT THE ASSISTANT STUDIES |
| 03 | The Kit | WHAT YOUR CAROUSELS PULL FROM |
| 04 | The Facts | PRINTS ON PACKETS AND OUTREACH |
| 05 | The Schedule | TOUCH WEEKLY |
| 06 | The Channels | WHERE YOU PUBLISH |
| 07 | The Machinery | HOW CATALOGING RUNS |
| 08 | Keys & Cloud | QUIET, BEHIND THE SCENES |
| 09 | The Team | STUDIO AND AGENCY TIERS |
Nine minutes, and the longest recording of the set. Settings is where the rest of the app takes its cues, so it earns the running time.
Open it from the sidebar, or press Cmd 5 from anywhere in the app. No Cmd comma.
Every row carries a three-digit number, its name in mono type, and its control on the right. The numbering is fixed. It walks the chapters in order and doesn't reflow when you open a fold or type in the filter. Simple rows edit right there on the line. Complex rows show a one-line summary and an UNFOLD link that opens a panel beneath the row. The rail at the bottom of the screen says it plainly: rows edit in place, no navigation.
At the top of the screen, on the left, sits your LOGO if you've set one. If not, your profile picture. If neither, a small pill with the workspace name. So the name in the header isn't always there. An image replaces it.
On the right of the header are three controls. The mode toggle, SIGN OUT, and SAVE SETTINGS. Most rows autosave a moment after you stop typing, and the button reads SAVING… then SAVED ✓ on its own. Clicking it forces the save immediately. Two rows are the exception and only save when you click their own Save button: CLIENT APPROVER EMAIL and WORKSPACE ANTHROPIC KEY.
Was this helpful
Still stuck
Tell us what happened and we will usually answer the same day. If it is more of a question than a bug, ask the room. Every tester reads it, and you are already signed in.