> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clickterm.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Version types & lifecycle
> Understand major vs. minor versions and how template lifecycle states (scheduled, effective, superseded) work.
When you publish a new template version, you choose whether it should be a **major** or a **minor** version. This choice determines how ClickTerm treats the version in terms of user consent and compliance.
## First version
The first version of every template is always a **major** version (1.0).
It becomes the baseline that all users must accept.
## Major versions
A **major version** is used when the content changes in a meaningful or legally important way.
When you publish a major version:
* All users must review and accept the updated terms again
* Previous consent no longer applies
* This version becomes the new baseline for future minor versions
**Use a major version when you introduce:**
* Updated Terms & Conditions
* New legal requirements
* Changes in user rights or obligations
* Significant policy updates
Major versions are labeled with whole numbers (e.g., **2.0**, **3.0**).
Publishing a major version resets the acceptance requirement for all users.
Your developers may need to handle re-acceptance flows.
## Minor versions
A **minor version** is used for small adjustments that do not require users to re-accept if they already accepted the latest major version.
When you publish a minor version:
* Users who accepted the most recent major version do **not** need to re-accept
* Only users who did not accept the latest major version will be prompted
* Typically used for small text updates or non-critical clarifications
**Examples of changes suitable for a minor version:**
* Fixing typos
* Updating formatting
* Clarifying non-legal wording
* Adjusting minor details that do not affect user rights
Minor versions are labeled with decimals (e.g., **1.1**, **1.2**, **2.1**).
Minor versions allow your team to keep the document up to date without requiring
additional acceptance events for the entire user base.
## Choosing a version type
When adding a new version, you will be asked to choose between **Major** and **Minor**.
If you are unsure, choose a **major** version. This ensures that all users explicitly accept the latest content.
***
## Template version lifecycle
When you publish a new version, you must choose an **Effective at** date and time. That timestamp determines when the new version becomes visible to end users. Until the effective time is reached, the previously effective version continues to be presented.
By default, the current date and time are preselected, allowing the version to become effective immediately. Alternatively, you can schedule the version for the future.
If a **scheduled version** already exists, any new version can only go live at least
**one hour after** the scheduled version's effective time. To go live sooner,
delete the scheduled version first.
Dates and times displayed in the ClickTerm UI are shown in your **browser's time zone**.
When processed, they are automatically converted to **UTC**.
### Lifecycle states
| State | When it occurs | End-user visibility |
| -------------- | --------------------------------------------------------- | -------------------------------------- |
| **Scheduled** | Effective at is set in the future | Not visible to end users |
| **Effective** | Effective at time has been reached for the latest version | Visible to end users |
| **Superseded** | A newer version's effective at time has passed | No longer shown; retained for auditing |
## Related
Create and publish template versions.
How version lifecycle affects SDK behavior.