Releasing

Saving keeps your team's work. Releasing makes a revision current for agents' documentation tools and, if the doc is shown on a live help center, public readers.

Members can write and edit docs. Only owners can release them. See Members.

Release an updated doc

1. Open the doc and review its title and body. Use Preview to check the rendered result.
2. Resolve any save errors shown in the editor.
3. Choose Release for a new doc, or Release changes for an update. Teaflask saves any remaining valid edits, then releases the saved revision.

The previous release remains in History as a superseded revision. Subsequent edits become working drafts rather than changing that released revision in place.

If this is the first release, the doc becomes available to agents whose enabled documentation tools and knowledge scope include it. If it is also shown on a live help center, its public page becomes available without a separate per-page publishing step.

Understand the revision history

During an editing session, autosave can update your own current draft instead of adding an entry for every save. After more than 30 minutes without a save, the next edit starts a new revision. Editing a released revision or another author's draft also creates a new draft rather than overwriting it.

History distinguishes four states:

• Draft: working content that has not been released. Your team can review and edit it.
• Published: the History badge for the currently released revision used by downstream readers.
• Superseded: a previous release replaced by a newer one.
• Discarded: a draft that was dismissed.

Released revisions are not amended by autosave. An agent reading a released doc does not receive your half-finished changes.

Restore an earlier version

Open History, select the revision you want, and choose Restore.

Restoration copies that revision into a new draft. Review and release it to make it current. The intervening revisions remain in history; restoring does not delete them or rewrite their contents.

Find saved changes that are not released

The Needs you filter in the Docs pane includes released docs with newer saved edits. It also includes proposed updates and documentation that needs verification review.

A doc that has never been released is labelled as a draft rather than appearing there solely because it is unreleased.

Verification and public visibility

A release requests verification of the new revision against connected code. Verification may still be running, be unable to check the doc, or fail to complete after the release has succeeded. Read the verification status separately from Released. See Verification.

Releasing content is separate from publishing your help center's design and settings, but it can still change a public page immediately. Before releasing sensitive content, check Show in Help Center and the scopes of agents that can read it. Hiding a doc from the help center does not hide it from those agents.

See Organizing for public visibility and Agent knowledge for agent scope.