Usage overview

Once a bundle is configured, editors work entirely from the rendered page.

Surface	What it is for
The on/off toggle	Turns the editing UI on and off, per user
Action links on each entity	Edit, and the operations the field allows
The sidebar	Holds the entity form, with save and preview
The add panel	Picks what to insert before or after an item

See Editing content for the toggle, the links and the sidebar, and Managing items for adding, moving, duplicating and deleting.

The toggle

Frontend editing is off until the editor turns it on, and the choice is stored per user. Where the toggle lives depends on the Enable on/off toggle in UI setting: on, it is a floating button positioned by the offset settings; off, it sits in the toolbar.

Switching it off adds the frontend-editing--hidden class to <body>, which hides the UI without reloading the page. The state survives page loads.

Administrators can set the starting position for users who have never touched the toggle with Enable frontend editing by default. A user's own choice always takes precedence once made.

What an editor needs

• The access frontend editing permission.
• A page that is not an admin route.
• An entity whose bundle is configured, showing its latest revision.

See Permissions for the operation-specific permissions. Content under content moderation is saved as a draft; see Content moderation.