Skill versions

Skill have versions! This allows for the creation of multiple dated versions of a single skill, without having to create a brand new skill.

This helps to control exactly when a new version goes into effect. It also automatically outdates existing results, prompting employees and managers to retrain.

Skill Versions let organizations easily manage evolving skills (like SOPs) by automatically expiring outdated results, and improving control, visibility, and auditability without the need to recreate skills from scratch.

How it works

The versions tab is on every skill page, and is located below skill levels, to the right of "History":

As can be seen above, when a skill is created, the version defaults to 1.0.

Each skill can have multiple versions, each with:

• A version name (for example: "2.0 - 2026 Update")

• A start date that determines when it becomes active

However - only one version can be active at a time.

To create a new version, click on the blue "+ Create new version" button. This will bring up the "Create new skill version" dialogue box:

Simply enter the desired version name, any relevant notes to the summary, and the date when you want the new version to begin. This can be today, or some day in the future.

All valid results pointing to the version will be automatically expired when a new version comes to life.

1. This includes all valid results - required and not. Note: Employee may have multiple valid results for a given skill. If not sure about the number visible in the yellow banner, best check the Skill result list

2. Number of expiring results may change compared to what users see in the dialog if the start date is at a later date.

3. Auto-achieved results for the target skill remain valid and unchanged unless a prerequisite (child) skill is revised.

Then finalize by clicking "Create new version". Once the start date comes, the old version will be deactivated, and will be listed as such under the "Versions" panel:

It is possible to roll back a new version to a previous one.

Details, rules and constraints

All plannings, requirements , personal requirements, revocations, exemptions, and prerequisite rules will continue to reference the skill itself. If the skill is included in any workflow, everything will continue to work exactly as before — the workflow will not be affected.

This means it does not matter which version is active or if a new version is starting — these objects will remain unchanged and continue pointing to the skill.

💬 Suggestion: If users want these objects to reference a specific version instead, they must archive the existing ones and create new objects with the correct active period.

In addition:

• If any skill definition changes are needed for the new version — such as updating the description, adding a new attachment — they need to be done manually, preferably on the start date.

• If some results already exist for a version, rollback isn’t possible until those results are deleted.

• You cannot delete a skill version, you can only rollback to the previous one.

Permissions

• Admins, Super users and users with edit rights on skills can create and manage versions.

• Other users with view access to the skill can view versions.