Page Settings is the fifth tab of the editor’s right rail, and it holds everything about a page that is not its body. Like the canvas, it autosaves: change a field and it is stored. There is nothing to submit.
Two things on this panel surprise people, so they are worth flagging before the field list. Adding someone as an author gives them edit access to that page even if their role would not otherwise allow it. And the AI generators here — for the summary, the keywords and the feature image — are free on every plan; there is no tier gate anywhere on this panel.
What each field does
| Section | Field | What it does | Can a page type require it? | Where it surfaces | More |
|---|---|---|---|---|---|
| Page Details | Slug | The page’s own URL segment | No | Site URL | URL Paths and Slugs |
| Page Details | Feature Image | The page’s lead image, plus its alt text | Yes | Site, listings, social cards | Asset Library |
| Page Details | Authors | The people credited on the page — and granted edit access to it | No | Site byline, editor access | Authors and Contributors |
| Page Details | Contributors | People who helped without a byline — also granted edit access | No | Editor access | Authors and Contributors |
| Page Details | Page Type | Which type the page belongs to, deciding layout, URL prefix and required fields | No | Site, URL, editor | Page Types |
| Page Details | Form | Attaches a form to the page | Yes — Required, Optional or Not Allowed | Site | Placing a Form on a Page |
| Page Details | Target Date / Published Date | The date you plan to publish; the real publish date afterwards | No | Plan calendar, site, listings | Publishing and Scheduling a Page |
| Page Details | Labels | Grouping, series membership and permission scoping | No | Site, listings, permissions | Labels and Series |
| Page Details | Journey | The funnel stage this page targets | No | Analytics, recommendations | Journey Stages |
| Metadata | Summary | One-paragraph description of the page | Yes | Search results, social cards, listings, on-site search, AI clients | Social Cards and Structured Data |
| Metadata | Keywords | Terms describing the page | Yes | On-site search, page metadata | Search for Your Documentation |
| Automations | Disable Dynamic CTA | Turns dynamic CTAs off for this page only | No | Site | Dynamic CTAs |
| Automations | Disable Autolinks | Turns autolinking off for this page only | No | Site | Autolinks |
| Redirects | Add Redirect | Extra paths that resolve to this page | No | Site | Aliases and Redirects |
| — | Revert Changes | Discards the revision in progress | — | Editor | Revisions and Versions |
| — | Delete | Removes the page, with redirect handling if it is live | — | Site | Managing Pages |
Page Details
The Page Details section is collapsible — the heading is a button — and open by default.
Slug
The slug is lower-case and dash-separated, and the field normalizes what you type as you type it: capitals are lowered, spaces and punctuation become dashes. A trailing dash is preserved while you are mid-word so the field does not fight you.
It is one segment of the finished URL, not the whole thing. The page type contributes its own slug, and any folder the page sits in contributes a segment for each level — URL Paths and Slugs shows how the parts compose.
Feature image
The Feature Image field appears only when the page’s type asks for one, so a documentation page normally has no feature image field at all while a blog post does.
With no image set you get one button, Set Feature Image, which opens the asset picker filtered to images. Once an image is set you get the image itself, a Change Feature Image button, and a Feature Image Alt Text field.
Beside the label sits a sparkle. It opens Generate Feature Image, which is the only place in Leed where image generation is mounted:
- Company Theme — pre-filled from your workspace’s AI theme and read-only until you flip the Edit toggle beside it. It is the standing description of how your images should look, so leave it alone unless this page genuinely differs.
- Palette (optional) — checkboxes for your brand colors, each with a swatch.
- Prompt — what you want in the image. Generate stays disabled until it has content.
Generating opens a second modal with the result, where you accept it or try again; accepting saves it to your asset library and sets it as the feature image. AI Image Generation covers the generator itself.
Authors and Contributors
Both are multi-select lists of people in your workspace, and they are mutually exclusive — add someone to one and they are removed from the other automatically. Authors are the public byline; contributors are the people who helped without one.
Page Type, Form, Labels and Journey
Page Type decides the page’s layout, the first segment of its URL, which fields are required, and which formatting controls the editor offers. It is locked once the page has been published — changing it would change the URL of a live page. Configure the types themselves at Configuring a Page Type.
Form attaches a form to the page. The select is disabled unless the page type says forms are Optional or Required for its pages — if it reads Not Allowed, there is nothing to choose. This is the page-level form, distinct from a form block placed in the body; Placing a Form on a Page covers both.
Labels do three separate jobs at once — grouping for listings, series membership for multi-part content, and a scope for permission overrides — which is why Labels and Series is worth reading before you invent a labeling scheme.
Journey tags the page with the funnel stage it is written for, which is what lets Journey Stages group your analytics and feed recommendations.
Target Date and Published Date
These are the same field wearing two labels. Before a page’s first publish it reads Target Date — the day you intend to publish, which is what puts the page on the plan calendar. It is a plan, not a commitment: nothing publishes because a target date arrives.
After the first publish the same field reads Published Date and carries the real one.
Metadata: Summary and Keywords
These two fields do more work than their size suggests.
Summary is the description in search results and social shares, the blurb on listing pages, part of what on-site search matches, and the text an AI client reads when it asks what a page is about. A page without one shows up in listings as a bare title. It is also required to publish a documentation page by default, so for a docs set it is not optional in practice.
Keywords are terms describing the page. Type one and press Enter to add it as a chip; click the × on a chip to remove it. Duplicates are ignored.
Each has a sparkle button beside its label. Generate Summary drafts a summary from the page body; Generate Keywords proposes a set the same way. The icon shakes while it runs, the field is disabled until it finishes, and the result lands in the field as ordinary editable text.
Generation is free on every plan, which is worth saying plainly because readers assume anything with a sparkle on it is a paid feature.
Everywhere the summary and keywords end up
The summary is reused in more places than any other field on this panel, which is why a lazy one is expensive:
- The
<meta name="description">on the published page, and therefore the snippet under your search result. - The description on your Open Graph and Twitter cards, next to the feature image — see Social Cards and Structured Data.
- The blurb beneath the title on any listing page that includes this page.
- Part of what on-site search matches and shows in its results — see Search for Your Documentation.
- The text an AI client reads first when it asks your documentation what a page covers.
Leave it blank and the site falls back to your workspace’s own description for the meta tag — so every page on your site claims to be about the same thing.
Keywords are narrower: they become the page’s <meta name="keywords"> and feed on-site search relevance. External search engines have ignored that tag for years, so there is no reason to stuff it — four or five terms a reader would actually type is the useful shape.
Automations
Two per-page switches that opt this page out of workspace-wide behavior:
- Disable Dynamic CTA — no dynamic call-to-action is injected into this page. See Dynamic CTAs.
- Disable Autolinks — this page’s text is not scanned for autolink terms. See Autolinks.
Redirects
Add alternative paths that resolve to this page — the old URL after a rename, a shortened marketing path, or the address a page had on the platform you migrated from. Type a path and add it; remove one the same way.
A path Leed will not accept opens an Error Adding Redirect dialog quoting the reason. Redirects are also what makes the link picker resolve an old address back to the right page. The whole model, including how redirects interact with page deletion, is on Aliases and Redirects.
Permission Overrides
The panel carries a Permission Overrides heading near the bottom. There are no controls under it today: per-page overrides are real and enforced, but the only way to grant one is through the API. The overrides you can grant from the CMS are on the resources themselves — Settings → Page Types and Settings → Labels each carry Content Manager, Approver and Contributor columns.
For most cases you do not need a per-page override at all: naming someone as an author or contributor grants exactly the same page-level Content Writer access from this panel. Resource-Level Access Overrides sets out the four override types and which surface grants each.
Revert and Delete
Revert Changes appears at the bottom of the panel only while the page is on version 2 or later and is not currently published — that is, while you have a revision in progress. It opens a confirmation warning that This will discard all changes made in this revision and restore the previously published version. This action cannot be undone. It means it: the in-progress revision is deleted and the previously published version comes back. Revisions and Versions covers when to use it.
Delete sits at the very bottom. For a page that has never been published it is a plain confirmation. For a live page it opens a larger dialog that requires you to choose what happens to the old URL, and lists every menu the page will be removed from. Managing Pages walks through it.
Both buttons need publish permission, along with most of this panel — see below.
Which fields need publish permission
Being able to edit a page is not the same as being able to change everything on this panel. With edit rights alone you can change the Slug, the Feature Image and its alt text, and the Authors and Contributors lists. Everything else — Page Type, Target/Published Date, Labels, Journey, Summary and its generator, Keywords and their generator, both Automations switches, Redirects, Revert and Delete — is disabled without page:publish on this page. The fields are visible but inert, so you can see what has been set without being able to change it.
The privilege can come from your role or from an override on the page, its page type or one of its labels; Roles and Permissions has the matrix.
Required fields
A page type can mark Feature Image, Form, Summary or Keywords as required for its pages. Click Publish with any of them missing and Leed opens Missing Required Fields, listing exactly what is absent under the line Before publishing, please provide the following in the page settings panel: — and refuses the publish until you fill them in. The server enforces the same list, so an API or MCP publish is refused too.
This is how a documentation set guarantees every page has a summary: summary is required by default for documentation page types, so a page cannot go live without one. A Form requirement is a three-way setting — Not Allowed, Optional or Required — and only Required blocks a publish. Which fields your page type asks for is set at Configuring a Page Type, and What Each Page Type Lets You Format covers its sibling setting.
When the panel is read-only
An API reference page built from an imported OpenAPI specification shows an amber notice at the top of this panel — Spec-driven APIs are read-only. — and its fields cannot be changed, because the specification is the source of truth. Regenerate the page from an updated spec instead; see API Reference Pages.
The same is true when you have no edit rights on the page at all, and when the page is published: a published revision is frozen everywhere, including here. Click Revise first. Autosave, Collaboration and Locking explains the three lock states.