Manage Versions of Project Templates
This guide explains how to manage different versions of a template in Authorium. Since there is no built-in version control yet, you can keep your templates organized using clear naming conventions, version notes, and archiving practices.
When to Manage Template Versions​
You should manage template versions when you need to:
- Update a published template without affecting existing projects.
- Keep a clear record of significant changes over time.
- Help teams easily identify the correct version of a template.
Note
Authorium is planning to introduce native version control in the future. For now, manual versioning is the recommended approach.
To Manage Template Versions​
- Use clear naming conventions
- For major changes (e.g., adding or removing stages): use whole numbers, such as
Contract Template v1,Contract Template v2. - For minor changes (e.g., field updates or visibility rules): use decimals, such as
Contract Template v2.1.
- For major changes (e.g., adding or removing stages): use whole numbers, such as
- Document version changes in the Description field
- Summarize what was modified in each version so other users can quickly understand the differences.
- Archive older versions
- Archive any templates that are no longer in use. This reduces clutter and prevents users from selecting outdated templates.
- Create a copy before making updates
- Copy the published template, make your edits in the new version, and publish it once testing is complete.
This approach ensures traceability and prevents confusion while allowing multiple template iterations to coexist.
- Copy the published template, make your edits in the new version, and publish it once testing is complete.
See Also​
To complement your knowledge of this process, check the following pages: