With versioning, users can:

• Layer minor changes safely without affecting live templates using the Save option

• Control what Create users can access by Publishing approved versions

• Track every version in a clear History log

• Restore previous versions if needed

• Port templates across servers (Organisation Support users only)

• Maintain governance with release notes and version tracking

Saving Templates

There is more than one way to save a template in Avvoka.

Clicking Save creates a minor version of the template. Each save layers changes and stores them as a new version. For minor saves:

The version number increases by a decimal (for example, 0.1 → 0.2)
The updated version number appears in the top bar of the Template Editor, opposite the template name
The version is stored in the History tab

Users in the Create area do not have access to ‘saved’ templates. The template would need to be published.

Publishing Templates

Publishing allows teams to make approved templates available in the Create area, control visibility, and maintain access to previous versions when updates are made. When a template is published for the first time:

The version number moves to v1.0
A release notes text box appears
The version number updates in the Template Editor top bar

Unpublishing a Template

Templates can be unpublished at any time. When a template is unpublished:

It is removed from the Create area
Users can no longer start new documents from it
Existing documents created from the template are not affected
The template and all versions remain saved

Unpublishing does not delete the template.

Before Publishing: Check Privacy Settings

Before publishing, ensure the template is not set to private:

Open the template in the Template Editor
Navigate to Template Details in the left-hand sidebar
In the Private setting, untick the checkbox
Click Save template

This ensures the template is visible to other users before publishing.

Release Notes

Release notes are prompted automatically whenever a new minor or major version is created. They:

Allow users to add explanatory text about what changed
Appear in the History tab
Are optional for both minor and major versions

History Tab

The History tab is located in the left sidebar of the Template Editor. In this area, users can:

View all saved and published versions
Identify the current published version
See who created each version
See when each version was saved or published
Read associated release notes

Whenever a new template is published, the version increases (for example, 1.0 → 2.0), and the History log reflects the update.

Restoring Versions

Users can select any previous saved or published version and choose to restore it. Restoring a template:

Makes that version the most up-to-date version
Updates the template to reflect the restored content

Archiving a Template

Archiving applies to the entire template. If a template is archived:

All associated versions are archived
Individual versions cannot be archived separately

Porting a Template (Organisation Support Only)

Porting is only accessible to Organisation Support users.

This feature enables support users to work on a template in one server and, once satisfied, release that version to a selected destination within the same organisation. To port a template: