Note: Hyperproof connects to many third-party systems that frequently change, including the system interface. Contact your System Administrator or the third-party provider for assistance in meeting the requirements to integrate with Hyperproof and collect the proof you need.

When you create a Hypersync between Hyperproof and Zendesk, you can automatically collect the following proof types:

Zendesk proof types and fields

Proof type	Fields	Testable
List of Groups	Name, Description, Default, Deleted, Created	No
List of Organizations	Name, Domain Names, Details, Created	No
List of Users	Role, Name, Email, Created at	No
Ticket Details	ID, Subject, Requested, Updated, Requester, Assignee, Status	No
View of Tickets	Satisfaction, Assignee updated, Updater, Organization, Solved, Due Date, Status	No

Additional documentation

Connection configuration

Authentication type: Custom

Custom authentication parameters: Zendesk Domain, Email, API Token

When you configure a Hypersync for Zendesk for the first time, you must provide the following information for the account you want to use to collect proof:

Zendesk Domain
Email
API Token

Tip: The API token required for authentication can be generated in Zendesk by clicking the Settings icon, then selecting API. Note that you must have Administrator privileges in Zendesk to generate an API token.

Note: You only need to connect Hyperproof to the app once, and then you can create as many Hypersyncs as you need.

Additionally, you can create multiple Hypersyncs for a single control or label.

Jira Cloud proof types

SentinelOne proof types and permissions

Zendesk Ticketing proof types and permissions

Dixa proof types and permissions

Trello proof types and permissions