![Hyperproof.Io [Test] Help Center](https://downloads.intercomcdn.com/i/o/xgk1dxp2/757668/427b255f2659cc7e0853d6a00ec1/628914ae2617199b7d999ba797a5305a.png)
There are two ways you can collect evidence (called proof in Hyperproof):
Manually, where you import proof and link it to a particular object, such as a control.
Automatically, where Hyperproof does the work for you.
Proof can be linked to objects like controls, control scopes, labels, and tasks, or you can import proof at the organizational level to use later on.
If you store proof in an external cloud-based service such as Google Drive or Dropbox, and want Hyperproof to upload a new version of your proof each time the source file is updated, it’s recommended to use the LiveSync feature. If you store your proof in an external service app and want Hyperproof to upload a new version OR upload a new file each time the source file is updated, it’s recommended to use the Hypersync feature.
Note: The Hyperproof PDF generator doesn't support non-Latin characters. When proof data containing non-Latin characters is converted to PDF format and uploaded to Hyperproof, blank spaces will replace those characters. For example, the Hyperproof PDF generator is used when you upload proof using a Hypersync or submit a questionnaire.
Tip: For more information, see the following videos at the bottom of the page.
Who can see proof?
Every piece of proof includes an editable facepile that lets you add users to the proof, view direct and inherited members, and view user roles.
Users with direct access have been explicitly added to the proof. These users do not need to have access to the root object or module, such as a control, to interact with the proof they’ve been added to.
Users with inherited access are connected to the proof by a root object or module, such as a risk. These users are not required to interact with the proof, but can if needed. What they can do in terms of permissions depends on their assigned role (manager or contributor). Click the link next to an inherited member’s email address to view the root object or module.
When a proof is made private, only users with direct access who have been added to it can open and preview it. Users who are members of objects linked to private proof can't open or preview the proof, but can see the proof name with a lock icon on proof lists. See Private proof.
For more information on access types, refer to Inherited access versus direct access.
Proof tab video for administrators
Watch this short video for information on managing proof.
Collecting proof video for compliance managers
Watch this short video for information on managing proof.
Collecting proof video for users
Watch this short video for information on managing proof.