What Leed Does Not Do

This page answers the question you were about to ask a colleague. Every entry says what does not exist, why the absence is deliberate where it is, and what to use instead.

It is one of three pages about the word “no”, and the difference between them matters. A feature that exists and misbehaves is on Known Limitations. A setting you cannot find in the CMS is named at Settings You Will Not Find. A number you want raised is on Limits That Are Not Plan Limits. This page is for capabilities the product does not have at all.

Accounts and sign-in

Three absences that are really one topic.

There is no password. No password field on the sign-in screen, no forgot-password link, no reset-password flow, and nothing in your profile that lets you set one. An account created through an invitation never has a password you could type.

There is no multi-factor authentication. No authenticator app, no TOTP codes, no passkeys, no SMS. There is no security setting to turn on, because there is nothing to turn on.

GitHub signs in accounts that already exist. It does not create them. Signing in with GitHub against an email that has no Leed account is refused with “GitHub sign-in only works for existing Leed accounts” rather than provisioning one.

What exists instead is the whole of the authentication model: a magic link emailed to you, or a one-time code emailed to you, or Google or GitHub on an account you already hold. A session lasts seven days and refreshes as you use it, and you can revoke any individual session — including one on a device you no longer have — from your Security tab. How each of those works in practice is Signing In, and the session and connected-account controls are Sessions, Connected Accounts and API Tokens.

Visitor privacy controls

Say that plainly rather than discovering it later. Exactly what is collected, tracker by tracker — page views, engaged time, clicks, scroll depth, media playback, element visibility, and the fingerprint used to recognize a returning visitor — is enumerated at How Leed Tracks Visitors.

One opt-out does exist, and it is worth naming so the paragraph above is not read as “no opt-outs at all”: every marketing email carries an unsubscribe link, and unsubscribing is honored for email. It has no effect on site analytics. That flow is Unsubscribes and Opt-Outs.

If you need consent behavior on your published site today, it is something you add in your own site templates — the templates are yours, and a banner that gates the tracker script is a template change rather than a product setting.

Appearance

Your published site and the CMS both follow the reader’s operating-system light or dark preference. There is no toggle — no switch in the header, no stored preference, and no theme attribute anywhere in the shipped templates. A reader who wants the other scheme changes it in their OS.

Authoring

There are no content templates. No “new page from template”, no starter-content picker, no snippet library, and no way to mark a page as a template for others to copy.

Three things exist that people often mean when they ask for templates, and it is worth being precise about which one you want.

A page type decides what fields a page has, what is required before it can publish, and how it renders — that is the closest thing to a content template and it is set once for a whole class of pages. Page Types covers it.

The Layouts workspace is a code editor over your repository’s template files. It is where the HTML around your content lives. It is not a content feature and there is nothing in it to pick from when you create a page. Layouts Workspace.

And an existing page can be reused the blunt way: copy its markdown into a new page. Nothing is generated for you, but nothing stops you either.

Limits nobody imposes

The mirror-image entry, and a welcome one. There is no traffic limit, no unique-visitor limit, no bandwidth limit, no storage limit, no seat limit and no page-count limit in Leed, on any plan. Editors and pages are unlimited on Free.

This is here because the question is asked constantly and the honest answer is that the limit does not exist rather than that it is large. The fixed ceilings that do exist — file sizes, query spans, rate limits — are all listed at Limits That Are Not Plan Limits, and the only three numbers that move with your plan are contacts, marketing emails and analytics retention.

Sold but not built yet

Five capabilities carry a tier on the pricing page and have no surface in the product: no screen, no API, and no MCP tool.

Feature (as the pricing page names it)Tier it is sold atWhat exists todayWhat does not exist
Agent & tool-call analyticsGrowthAggregate AI and MCP traffic reporting, free on every plan — Analytics for AI and MCPPer-agent or per-tool-call breakdowns of what agents asked your docs
Account-based qualificationEnterpriseAccounts, personas and engage scores — AccountsAny account-level qualification model, scoring rule or routing built on it
Cluster analyticsEnterprisePer-page and per-journey analytics on the Know dashboardAny grouping of content into clusters, or reporting across one
CRM integrationEnterpriseA single inbound Salesforce webhook with per-customer handling — CRM IntegrationA self-serve connection panel, field mapping, or two-way sync
SSO & audit logEnterpriseMagic-link, one-time-code, Google and GitHub sign-inSAML or OIDC single sign-on, and an audit log — see Settings You Will Not Find for the audit log, which the pricing page bundles into this one row

CRM integration is the one row with something real behind it, and CRM Integration spells out what that something is so an Enterprise buyer is not left guessing. What each tier really includes, feature by feature, is Feature Availability by Plan.

Where the other kinds of “no” live

What you are looking forWhere it is
A setting that is not in SettingsSettings You Will Not Find
A feature that exists but does not behaveKnown Limitations
A number you want raisedLimits That Are Not Plan Limits
ESC