Drafts

Drafts collect work in progress: pages and other artefacts that are not yet published to a live Space or channel. Use Drafts to iterate without changing what visitors see on production routes.

What shows up in Drafts

Anything saved as draft or left unpublished in Create (and related modules) can surface here, depending on product configuration:

• Page edits in the canvas that have not been published.
• New pages or routes started from a Space but not yet live.
• Cross-module ideas that are not ready for Engage or public traffic.

The Drafts desk is a single place to resume work (/dxp/create/drafts) instead of hunting inside each Space.

Draft vs published

Draft means the engine and edge do not treat the content as the live view for public URLs. Publish (or equivalent action in the desk) promotes the version visitors should receive and participates in cache invalidation on the edge.

Always confirm which Space and route a draft targets before publishing; hostname and path resolution are Space-scoped.

Collaboration and safety

Drafts are visible to operators with Create access on the organisation. They are not a substitute for member-only or staging hostnames if your deployment uses those for review—use the routing model your operator runbook describes.

Related Create areas

• Spaces — destinations where published pages go live.
• Library — shared assets drafts can reference before publish.
• Pages and editor — autosave, publish, and restore flows.