SupportPublish a Piece version
Turn a reviewed Piece revision into an immutable published version after validation, Arena testing, and required approval.
How this fits into Lead360Explore Ask360 Piece StudioUnderstand the commercial operating model behind versioned Ask360 roles.- 01
How Lead360 helps
- 02
Before you begin
- 03
Complete the workflow
- 04
Understand the key controls
How Lead360 helps
Piece publishing records an immutable version of the reviewed revision. It gives consumers and auditors a stable identifier for identity, capabilities, business data, behavior, safety, and model configuration without allowing later draft edits to rewrite what was published.
When to use this workflow
Publish only when the exact revision has completed validation, realistic Arena testing, required certification, and business approval.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Confirm the intended revision identifier and final diff.
- Review validation, Arena, certification, source, and approval evidence.
- Identify every consumer that may later move to the new version.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Open Versions and audit for the intended Piece.
- Compare the draft revision with the current published version.
- Confirm validation, required Arena certification, and reviewer approval.
- Publish the exact revision and record the immutable version identifier.
- Update each intended consumer separately and verify its behavior.
Understand the key controls
Immutable version
Publishing creates a stable version. Future edits belong to new draft revisions and cannot rewrite published history.
No automatic consumer update
Publishing does not automatically update Automations, Chat Widgets, bots, or other consumers.
Audit evidence
The version should retain who published it, when, from which revision, and what changed.
Approval boundary
Publication approval applies to the reviewed revision. It does not approve later consumer assignment, channel activation, or unrelated workflow effects.
Confirm the result
Do not rely on a success message alone. Confirm the saved state and any live effect in the product area that owns the final record.
- Confirm the new version appears in version history.
- Compare its configuration with the approved revision.
- Verify each updated consumer points to the intended version.
Troubleshooting
Publish is blocked
Resolve validation, certification, permission, resource, or revision-state requirements shown by the product.
Live behavior did not change after publishing
The consumer may still reference the prior version. Update and test that consumer explicitly.
Frequently asked questions
Does publishing update bots and automations automatically?
No. Consumers remain on their current version until an authorized user updates each one.
Can a published version be edited?
No. Create a new draft revision, repeat review and testing, and publish a new immutable version.
Continue with Lead360
Use this workflow in Lead360
Put this guide into practice with a 14-day free trial of Lead360 Pro early access, or continue learning through the related collection.