Use framework versions to separate working changes from reviewed copies. Open the version button in the framework header to inspect history, select a version and see the actions available to your role.
Create a new version
From the latest version, choose New minor version or New major version. The confirmation previews the new version number and identifies the source version being copied. Review it before choosing Create version.
The new version is an editable working copy. Creating it does not automatically approve it. Use Name this version or Rename this version for a useful human label; this changes the label, not the numeric version identifier.
Submit and decide
Resolve pending requirement edits before beginning a workflow action. Choose Send for approval on an in-progress version and review the confirmation. The pending state locks assessment editing while the configured approval process is followed.
Authorised approvers can Approve or Reject, with a decision comment where offered. Approval preserves the reviewed copy. Rejection archives that version; prepare a new version to address the feedback. Return to editing withdraws a pending approval request when the action is available.
Each state-changing action has a confirmation. Read the result and the updated version status; opening the confirmation alone does not execute it.
Configure approval
Open Settings → Approvals and review the framework version approval row. Enforcement, the approver role and whether one or all eligible approvers must act determine the workspace workflow. Configure member roles under Settings → Members and Roles.
Make sure the selected role has the intended active approvers. A contributor's edit permission does not automatically make them an approver.
Read or remove history
Select a previous version from the menu for reference. Historical, approved and pending copies have editing restrictions; use the current editable version for new assessment work.
Historical-version deletion is offered only where permitted and requires confirmation. It permanently removes that version and its contents. Review retention needs and the selected version number before confirming; deleting a version is different from deleting the entire framework.