Skip to main content

Version Management

Coming Soon

The ability to publish a new version of a live template — and automatically re-prompt users who accepted an earlier version — is currently in development.

In the meantime, the workaround below explains how to update a published template's content today.

Updating a Published Template Today​

You cannot edit the content of a published template directly. To make changes, create a copy, update it, and switch your deployment over to the new version.

  1. Open the template you want to update.
  2. Click ⋯ → Clone. A Draft copy is created with all the existing content and settings.
  3. Give the clone a clear name that distinguishes it from the original — for example, Terms of Service — March 2026.
  4. Make your changes in the new Draft.
  5. Click Publish.
  6. Go to Deployments, open the active deployment, and update the Template field to point to the newly published version.

Users on that deployment now see the updated content. The original template and its acceptance records are unchanged.

Coming Soon

Screenshot: Template ⋯ menu showing the Clone option on a Published template

tip

Users who already accepted the previous version are not automatically re-prompted. If your update is significant enough that existing users need to accept again, coordinate with your legal team on the appropriate approach until the Re-consent feature is available.

What Versions Already Track​

Even though the full versioning workflow is not yet available, every acceptance record already captures which version of the template the user saw at the time. This means you have a complete historical record — including for agreements accepted before versioning ships.

What Is Coming​

When versioning is fully released:

  1. Open a published template and click New Version.
  2. A Draft copy is created with the existing content pre-loaded.
  3. Make your changes.
  4. Publish the new version.
  5. Optionally enable Re-consent on Update — users who accepted an older version will be prompted again on their next visit.

Existing acceptance records will remain permanently tied to the version the user originally saw. Updating to a new version will not alter past records.

Next Steps​