How Confluence Cloud Handles Deleted Versions
When a page version is deleted in Confluence Cloud, the platform automatically re-numbers the remaining versions to maintain a continuous sequence. This behavior depends on which version is removed. For example:
-
Deleting Version 1 (when versions 1, 2, and 3 exist)
-
The old Version 2 becomes the new Version 1
-
The old Version 3 becomes the new Version 2
-
-
Deleting Version 2 (when versions 1, 2, and 3 exist)
-
The old Version 1 remains Version 1
-
The old Version 3 becomes the new Version 2
-
Confluence does not preserve gaps in version numbers, and remaining versions are shifted and renumbered accordingly.
How QC Approvals Handles Renumbered Versions
QC Approvals continues to track approvals correctly even after Confluence renumbers versions.
This is because our app identifies page versions using their creation timestamps, not their version numbers.
Even if Confluence shifts the numbering (for example, due to deleting a version), QC Approvals still knows which content was approved and preserves its approval status.
Preventing Users from Deleting Page Versions
If you want to avoid accidental or intentional deletion of versions, Confluence Space Administrators can disable the "Delete" permission for users within that space.
You can disable permissions either for individual users or user groups.
To disable permissions for individual users, follow these steps:
-
Go to “Space settings” and from the “Space access” menu select “Users”.
-
Click on the “Edit” button.
-
Find the user that you do not want to be able to delete page versions, and make sure that the “Delete” checkbox is unchecked.
-
Click “Save”.
To disable permissions for groups, follow the steps below:
-
Go to “Space settings” and from the “Space access” menu select “Groups”.
-
Click on the “Edit” button.
-
Find the group that you do not want to be able to delete page versions, and make sure that the “Delete” checkbox is unchecked.
-
Click “Save”.