Standard
The family describes expected configuration and its version.
Advanced capability
Change the system without losing the way back.
For authorised implementation and administration teams: a versioned path intentionally hidden from normal navigation.
Visibility
The configuration fleet stays advanced and hidden
Not a daily settings screen
These advanced configuration tools are reserved for administrators and do not appear in normal navigation.
They open only to authorised implementation and platform roles with explicit scope.
Prepare
Compile families, instances and overrides
Instance
The deployment associates the standard with the relevant client, site or domain.
Override
A deviation is named, scoped and reviewed rather than disappearing in a copy.
Analyse
See impact before the campaign
Analysis compares
- active and proposed versions
- affected scopes and overrides
- dependencies, validations and generated work
The approver receives
- a readable change
- risks and validation gates
- rollout and rollback plans
Roll out
Approve, target, observe
- Approval
The authority accepts the version and its scope.
- Targeting
The campaign names the instances to upgrade.
- Rollout
The new version is rolled out in controlled batches, with the status of each one visible.
- Observation
Errors, work and outcomes remain attached to the campaign.
Rollback and coordination
Return to a known version
Going back to an earlier version also needs approval
Rollback targets a recorded version, preserves the reason and follows the same authorisation gates.
Generated workflows and task actions remain in their domains; configuration does not bypass business authority.
Prepare one controlled change
Name the standard, instances, approver, first rollout batch and rollback version.