![Hyperproof.Io [Test] Help Center](https://downloads.intercomcdn.com/i/o/xgk1dxp2/757668/427b255f2659cc7e0853d6a00ec1/628914ae2617199b7d999ba797a5305a.png)
Roles and permissions:
The following roles can create or maintain Hypersyncs:
Anyone with manager or contributor permissions for a control or label
The first step in creating a Hypersync is selecting the app where you will access the data for the proof. We use the term application/app to refer to sources like AWS or GitHub.
If this is the first time a Hypersync is created for an app, you are prompted to establish a connection between Hyperproof and the app. You need to enter their credentials that authorize Hyperproof to access the app, as well as limit the permissions/scope granted.
After the connection to the app has been established, future Hypersyncs may simply reuse it. Connections can also be shared. One Hyperproof user can establish the connection, and then decide what other user may create Hypersyncs with that connection. This workflow is helpful because it eliminates the need to re-enter credentials.
App credentials are typically issued by the organization's IT admin. The rest of this document is designed to help both the Hyperproof user and the IT admin understand how Hypersyncs work and the steps necessary to get them up and running.
Note: A Hyperproof user may already have personal credentials for an application. These credentials can be used to establish a connection for Hypersyncs without requiring involvement from IT. This makes it easy to get started, but is NOT recommended long term. For long term continuity and maintainability, it’s recommended to use service accounts set up by your IT department.
Workflow
Note: For any given app, many different proof types can be generated to satisfy different compliance requirements and controls. At this time, there is no way to see a sample of the proof types in the app without actually setting them up. If you can’t find the proof you need, reach out to us in our forum.
Tip: Many proof types have criteria to narrow the information collected. For example, you may see criteria specific to both the app and the proof, such as user types, repositories, and severity. The criteria used are shown in the proof.
Go to the control or label you want to link to a Hypersync.
Select the Automations tab, then click Create Hypersync.
Use the filter at the top of the Choose apps window to find and select the app where the proof data will be pulled from, e.g., Azure or GitHub. You can search for apps by Name, App ID, or Category, such as Ticketing or Accounting apps.
Provide credentials if a connection has not already been created.
Select the specific proof you want to collect.
Configure:
The Hypersync's schedule (when it runs)
Whether the proof should be versioned or added as a new file
The output format (PDF or Excel)
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.
A name for the proof (which is also the name of the Hypersync)