Product · Publishing
Agents draft. People publish.
Writing and publishing are separate permissions in HelmCMS. Every save is an immutable version, previews read drafts through their own key, and the live site only ever sees published content.
Part of our guide What is an agentic CMS.
Immutable versions
Every save is a new version; restore any earlier one as a new draft.
Publish is a permission
Authors write, editors publish. Give agents the author role.
Draft previews
A preview key reads drafts; the live key never does.
01No silent overwrites
When two people, or a person and an agent, edit the same record, the second save with an outdated version is refused with a conflict instead of replacing the other change.
02A record of every change
Write and publish actions go to the site's audit log with the actor, the action and the outcome. The record's Info panel shows who created, edited and published it.
- Publish, unpublish and delete need the editor role
- Unpublishing removes the entry from the delivery API
- Webhooks fire on publish, unpublish and delete
MCP tools
What your agent can call here
- create_entry
- update_entry
- list_versions
- restore_version
- publish_entry
- unpublish_entry
Questions
Is there an approval queue for agent changes?
Not yet. Today the role split does the job: agents signed in as authors can only draft, and an editor publishes. A dedicated review queue is on the roadmap.
Can I schedule publishing?
Not yet; scheduled publishing is planned.
Back to the guide: What is an agentic CMS?
Keep exploring