Understand versioning on policies

Learn how versioning applies to policies.

Every time a policy is updated, a new version is created. Versions are snapshots of the contents of a policy at a particular point in time, including the policy file and policy information. Every version has a version number and can be found in the version history.

Who does this article apply to? 

In this article: 


Policy versions

Every time a policy is updated, a new version is created. Versions may be major or minor, depending on how changes were applied at the time the policy was updated:

  • A major version is created when the policy is first created and when an updated policy requires re-acknowledgement, otherwise a minor version is created.

Version numbers

A version number is a system-generated number that uniquely identifies a policy version. The version number of a policy takes the form X.Y.Z, where X, Y, and Z are whole numbers that increase over time as a policy is updated:

  • Whenever X increases, users were required to re-acknowledge the updated policy. This signals a major version change. 
  • Whenever Y increases, users were notified about the updated policy. This signals a minor version change.
  • Whenever Z increases, users weren't notified about the updated policy. This also signals a minor version change. 

Version history

A policy's version history provides access to previous versions, as well as information about who published each version and when. Also included in the policy version history are the notes made at the time the policy was updated and a record of how changes were applied.


 

If you found this article helpful, let us know by selecting "Yes" or "No" below. If you require further support, please contact Manager Support.