Keka proof types and permissions
Note
This Hypersync is not supported in Hyperproof Gov.
When you configure a Hypersync for Keka on a control or label, you can automatically collect the following proof types:
Requirements
To connect to Keka and collect proof, your Keka configuration must meet the following requirements.
You must be a Keka administrator.
Subdomain - The subdomain for your Keka account. For example, if you sign in at
acme.keka.com, your subdomain is acme.Client ID, Client Secret, and User API Key - Contact a Keka sales representative and make sure you have the API > Webhooks Add-On , or you will not be able to complete the configuration.
In Keka, click the gear icon to open Settings.
Under Integrations and Automation, navigate to the API Access tab and enable API Access.
Copy the Client ID and Client Secret and store them in a secure location.
Click Create key to create your API Key.
Copy the API Key and store it in a secure location.
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.
Connection configuration
When you configure a Hypersync for Keka the first time, you must provide the following information:
Account Data - Production or Sandbox account data.
Subdomain
Client ID
Client Secret
User API Key
The first time you run this Hypersync, it may take up to 24 hours to load all employee data.
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.