We've simplified publishing in the console to make content management more intuitive—whether you're updating a single Object or coordinating changes across multiple Spaces and Points of Interest. The updated statuses and terminology align with publishing workflows used in other systems, helping you clearly see what’s live in the PWA and what’s still in progress.

What’s New

We’ve updated a few key terms in the Pladia Empower Console to make the publishing process clearer:

On-Display / Off-Display are now Publish and Revert to Draft.
- Use Publish to prep content for release to the PWA.
- Use Revert to Draft to mark content for removal in your next release.
Publishing a public bundle is now called Releasing a public bundle, to better reflect how changes are grouped and pushed live together.

You’ll find the Releases button at the top of your console screen—this is where you can manage and send updates live across all connected apps.

New Statuses, Explained

Here’s how the updated statuses work, in the order you’re most likely to encounter them:

📝 Draft

You’ve created a new Object, Space, or POI and saved it, but it’s not live in the PWA yet.

Status shown:

What it means: The content is saved in the console but hidden from your public PWA.
What to do next: When you’re ready for it to go live, click Publish.

🔁 Out of Sync - Published

You clicked Publish, but the content hasn’t appeared in the PWA yet.

Status shown:

What it means: The asset is marked to go live, but it won’t be visible in the PWA until it’s included in your next public release.
Why this matters: The sync icon means the console and the PWA are temporarily out of sync.
What to do next: Head to the Releases screen and push a public release.

✅ Published

The asset has been released and is now live in your PWA.

Status shown:

What it means: The version you see in the console is exactly what visitors see in the PWA.
No further action needed unless you want to make updates.

✏️ Published with Draft Changes

You’ve saved edits to an item that’s live in the PWA, but haven’t marked them ready for release.

Status shown:

What it means: The current version remains live in the PWA. Your draft edits are saved in the console but are not yet able to be included in a release bundle.
What to do next: When you’re ready, use the Publish button to prep the updates to be included in the next public release.

🔁 Published with Changes (Pending Release)

You made updates to something that’s already live in the PWA and hit save.

Status shown:

What it means: The original content is still visible in the PWA, but your changes aren’t yet.
What to do next: Include this item in your next public release to sync the updates to the PWA.

🔁 Draft (Pending Release) (After Revert)

You’ve decided to unpublish the item.

What you did: Clicked Revert to Draft on an item that was previously published.

Status shown:

What it means: The item is still showing in the PWA but it will be removed the next time you publish a release.
What to do next: Perform a public release to remove the item from view.

💤 Draft (Again)

The item has been removed from the PWA.

Status shown:

What it means: After the latest release, this item is no longer visible in the PWA. You can continue editing it or leave it as-is.

✅ Need a Refresher on the New Terms?

Publish → Prepares an asset to go live in your next release.
Revert to Draft → Removes an asset from the PWA in the next release.
Public Releases → Formerly “Publishing a public bundle,” this pushes all pending changes live in one batch.

Why We Made These Changes

This update reduces confusion and aligns with standard publishing models. If you’ve worked in other headless or content systems, the draft → publish → release flow will feel familiar—and easier for teams managing many content pieces at once.

Need Help?

If you’re unsure whether something is live or still in draft, check the status icon in the top right corner. Clicking on the information symbol will give you additional details.