If you're noticing that the policy version ID in Hyperproof isn’t updating when changes are made to a LiveSynced SharePoint document, this is expected behavior.
Hyperproof uses two version identifiers:
Policy version ID (e.g., V1): This represents the version of the policy itself.
File version ID (e.g., v4): This tracks the version of the source file attached to the policy.
When LiveSync is enabled, only the file version ID is updated to reflect changes made in SharePoint. The policy version ID remains the same while the policy is in the Draft stage.
Why the policy version ID doesn’t change
Only one draft policy version can exist at a time.
LiveSync allows the source document to be updated without requiring a new policy version.
To create a new policy version, the current draft must be manually marked as Effective or Retired.
This avoids unnecessary version inflation from minor document changes.
Steps to confirm this behavior:
Create a policy.
Click + Add version, select Draft, and assign a version ID (e.g., V1).
Select Edit in Hyperproof.
Click + Add policy document and attach your SharePoint file.
Toggle Live sync to On.
Make changes to the document in SharePoint.
Refresh the Document tab in Hyperproof.
You’ll see that the file version updates (e.g., v3 → v4), while the policy version stays the same (e.g., V1).
For more details, view our documentation:
Understanding policy versions in Hyperproof
Still have questions? Email us at support@hyperproof.io and we’ll be happy to help.