Payload CMS admin vs on-page editing: when to use which
Payload gives developers a typed, code-first CMS and editors a clean admin. For creating a page or modelling a new collection, the admin is the right place. For changing one sentence on a page that's already live, it's a long way round.
What Payload's admin does best
Payload's admin is generated from your config: every collection, field, validation rule and access function you define in code shows up as a clean, typed form. That makes it the right place for:
- Creating content — a new article, product, event or page, with every required field filled in.
- Structure — blocks, relationships, arrays, nested data.
- Bulk work — lists, filters, versions and drafts across many documents.
- Settings — globals, users and anything that isn't visible on a page.
Where the admin is a long way round
Now take a typical request: “the second paragraph on the services page sounds stiff — can we make it friendlier?” In the admin, an editor has to work out which collection the page comes from, find the document, find the field (perhaps inside a block, inside an array), make the change without seeing it in context, save, and go back to the site to check. If they get the wrong document, nothing visibly happens.
Payload's live preview narrows that gap by showing the page next to the form. But the editing still starts in the admin, with the form as the main surface.
What on-page editing adds
The payload-vibe-editor plugin flips it: the editor starts on the page. They turn on edit mode with a switch, click the paragraph, ask for a friendlier version or type it, see it in place, and save. Behind the scenes:
- The plugin adds a few authenticated endpoints to Payload (
/api/vibe/suggest,/save,/swap-image,/generate-imageand/status). - Your front end marks editable elements with
data-vibe-*attributes that name the collection, document and field. - A small overlay — plain JavaScript and CSS, no build step — loads for signed-in admins only.
Your access control still decides
This is the part that matters to developers. On-page editing in Payload is not a side door:
- Every read and write goes through Payload's Local API with
overrideAccess: falseand the requesting user, so your access functions have the final word. - Before any AI call or save, the user must be able to read the document and pass the collection's update access. A change that would be refused costs no credits.
- Only fields you list in
allowcan be written at all. - The developer key lives in your server environment and never reaches the browser.
What editors can change on the page
- Text fields — rewritten with AI or typed. For a Lexical rich-text field, the new text replaces the field's text as one plain paragraph, so it suits short rich-text fields better than long formatted articles.
- Pictures — generated with AI (stored in your uploads collection), pasted as a URL, or picked from the media library.
- Alt text — saved on the upload, so it changes everywhere that upload is shown.
- Page title and meta description — by default in the fields
@payloadcms/plugin-seoadds.
A sensible split
| Task | Use |
|---|---|
| Create a new page, article or product | Payload admin |
| Change blocks, relationships or page structure | Payload admin |
| Long, heavily formatted rich text | Payload admin |
| Fix or rewrite a heading or paragraph | On the page |
| Swap a picture or write its alt text | On the page |
| Improve a page title or meta description | On the page |
Both paths write to the same documents with the same permissions, so there's nothing to keep in sync. Developers keep Payload exactly as they designed it; editors get a faster way to do the small things. If your front end is Next.js without Payload, the Next.js adapter gives you the same editing on your own database.
Try now