Skip to main content

Versioning versus new files

Written by Hyperproof Support
Updated over 3 weeks ago

When you create a Hypersync, you can choose how you want to add proof, either by versioning or new files.

It’s recommended to select versioning when you want updates to replace the existing proof. The older proof is still accessible, but the latest version is the most current. Proof that contains settings like a password policy are good candidates for versioning since you typically care most about the current settings.

New files should be used when you don’t want to replace the existing proof. This is generally used when the proof contains data for a period of time such as backup jobs and pull requests. Typically, you’d want to keep the data collected for each month in separate files that are easily accessible.


💡 Tip

Hyperproof recommends a default when you create a new Hypersync. If you’re not sure which option to choose, you can leave the default.

To switch to a different option, go to the appropriate control or label, then select the Automations tab. Mouse over the Hypersync you want to edit, and then click ... (Menu) > Settings. See the screenshot below.


change-settings.png



A note about proof versioning

If the file was uploaded using a Hypersync, Hyperproof displays the Hypersync icon with the last sync date and time. If the icon is green, the Hypersync is healthy.

See Managing Hypersync connection health for more information.

Note that if versioning is enabled on Hypersync-collected proof, Hyperproof only uploads new proof when the actual data changes. However, the Last sync date is updated whether or not the data has changed.

See What does Hypersync proof look like? for more information.


💡 Tip

Only the proof owner can upload a new version of proof and see the Provide this version button.


Did this answer your question?