Settings You Will Not Find

Seven cards were designed for the Settings grid and deliberately not built, because nothing sits behind them yet. A handful of other settings are ones people arrive expecting from other tools, and Leed simply does not have. Both lists are short, and naming them is faster than searching four times and concluding the search is broken.

Every row below ends somewhere. Some of these are absences with a good alternative, some are absences with a workaround, and a couple are genuinely missing. The page says which is which.

Cards that were designed and not shipped

Audit log

Leed does record an audit entry for every create and update, carrying the actor, the change and the resulting value. What is missing is the read path: the audit provider exposes a write method and nothing else, and no API route serves the records. So the data exists and you cannot see it.

The closest things you can read yourself are a page’s own history at revisions, versions and reverting, and the record of what went live when at deployment history and status.

Agents

There is no agent configuration screen, because there is nothing to configure. The AI surfaces you actually have are the Chat tab in the rail (its composer limited to administrators), the Assistant inside the page editor, the Operator MCP — which you connect a client to rather than configure — and the Docs MCP for your readers, whose only two settings are the toggles inside Settings → General.

Everything the AI can do, and the permission model behind it, is at how Leed’s AI is guarded; the two toggles that genuinely are settings are at configuring the Docs MCP.

Webhooks

Leed has no outbound webhook configuration. It receives webhooks — from its own build infrastructure and from vendors — but there is nothing you can point at an endpoint of your own.

What people usually want a webhook for has two working answers here. If you want to be told about a form submission, a form’s internal notification email list does that job — see building a form. If you want to pull data out on your own schedule, connect an MCP client and query it: what the Operator MCP can do.

Templates

A Templates card was designed; there is no content-template feature behind it. Layout files are edited in the Design workspace, and a new page type generates its own scaffolding when you create it — so the two things a content template would have given you already exist, just not under that name.

API

There is no API-keys settings screen. API tokens are real and they live on your profile → Security, not in Settings — sessions, connected accounts and API tokens. The CLI does not use a pasted key at all; it signs in with a device code, described at CLI authentication.

There is also no published REST API reference — the backend’s OpenAPI document endpoint is disabled in the shipped build. The two supported programmatic surfaces are therefore the CLI, at installing the Leed CLI, and MCP, at the Operator MCP tool index.

Deployments

Not a settings card because it is a whole workspace: Deploy in the rail. How publishing works is the end-to-end account of what happens when you press the button.

Integrations

There is no integrations screen. The two integrations that exist are reached from the place they apply: Domain Connect, a button beside the Domain field on general site settings and explained at domains and DNS, and connecting a GitHub account for sign-in, on your profile’s Security tab.

Your profile also carries a Connect LinkedIn Profile button under Social Profiles. It is not wired up yet — clicking it does nothing. Set your LinkedIn handle on the Socials section of Settings → General instead if what you want is the icon in your site footer.

Settings other tools have that Leed does not

Time zone and language

The General card’s own description promises “time zone, default language”. Neither field exists — not on that screen and not anywhere else in the CMS.

Your workspace record does carry a time zone and a locale, and both are set when the workspace is provisioned. The time zone is what a date format ending in z resolves against, and when it is unset the site build falls back to UTC. One place uses a different fallback: form-notification emails format their timestamps in America/New_York when no zone is set, so a submission notification can carry a different clock from the same date on your site.

If a rendered date is in the wrong zone, that is the reason. Today the fix is a support request rather than a setting. The date formats themselves, and which of them print a zone abbreviation, are at default content configuration.

Password, MFA and session policy

Leed has no passwords, so there is nothing to configure. Signing in is a magic link, an emailed code, Google, or GitHub — every route is covered at signing in.

You can review and revoke your own sessions on your profile’s Security tab, at sessions, connected accounts and API tokens, and you can authorize a device or an MCP client at authorizing devices and clients. What does not exist is a workspace-wide session lifetime, MFA requirement or sign-in restriction that an administrator sets for everybody.

Notification preferences

Per person, on your own profile — your profile. There is no workspace-level notification configuration, so an administrator cannot set what colleagues are emailed about; each member sets their own.

Which screen you land on at sign-in

Leed remembers a home preference in your browser and defaults to Know. Nothing writes it, so there is no way to change it from the UI. Bookmark the tab you prefer instead; the rail and its six destinations are described at touring the workspace.

Cookie consent, analytics opt-out and a dark-mode toggle

Three things a visitor-facing site is often expected to have, that a Leed-published site does not ship.

There is no consent banner and no visitor-facing analytics opt-out; how Leed tracks visitors states the privacy posture plainly so you can decide whether you need to add one yourself. Dark mode follows the reader’s system setting with no toggle to click, which is a deliberate choice explained at dark mode.

Things that look like settings and are not

Three surfaces exist and do less than their name suggests. Each one has cost somebody an afternoon.

Automations configures exactly one thing — the auto-linking word list — despite a card description promising rules that publish, route or notify on triggers. The screen you land on is titled Auto-Linking, which is the honest name. It is documented at autolinks.

Emails is a read-only list of email templates, not sender-domain or suppression configuration. Editing happens on the email layout canvas, at email layouts. Unsubscribes and suppression are real and they work — they are just not on this card, and are covered at unsubscribes and opt-outs.

If you were looking for something else

If your setting is not on this page, it is probably on the map. Settings home and the settings map lists all thirteen cards, the route each one opens, and the page that documents it, plus a second table for the configuration that lives outside Settings entirely — your profile, the editor’s right rail, the Design workspace and the Deploy tab. If you are working backwards from a symptom rather than a setting name, start at the troubleshooting index; and if you want this page’s honesty applied to the whole product rather than to the Settings grid, that is what Leed does not do and known limitations.