Skip to main content

Workday proof types and permissions

Written by Hyperproof Support
Updated this week

Hyperproof uses Merge, a third-party API, to retrieve data from HRIS apps. Hyperproof uses the Employees, Employments, and Groups scopes. If you are interested in learning more about the permissions needed for HRIS Hypersyncs that use Merge, refer to the Merge Authentication Guides page in their Help Center.

Note: This Hypersync is not supported in Hyperproof Gov.

When you configure a Hypersync for Workday on a control or label, you can automatically collect the following proof types:

Workday proof types and fields

Proof type

Fields

Testable

Employees with Change in Employment Status

Name, Email, Department, Title, Status, Start Date, End Date, Last Day of Work

Yes

List of Employees

Name, Email, Department, Title, Status, Start Date, End Date, Last Day of Work

Yes

This Hypersync supports importing a company directory for an access review. See Importing a directory with a Hypersync for more information.

Blocking sensitive data

The best practice for setting up access to Workday is to use a Workday Integration System User (ISU), a specialized, non-human account designed to securely run scheduled integrations, reports, and API processes. Your Workday admin can restrict what Merge can read by excluding fields that they don’t want Merge to access. For example, you could exclude “Person Data: Personal Data” and “Person Data: Home Contact Information” to limit the fields visible to Merge from these domains. Detailed instructions are available in this Workday HRIS Permissions guide.

Requirements

Note: This Hypersync supports SFTP connections. For ease of use, Hyperproof recommends using the API connection instead. If you would like to use the SFTP connection option, refer to the HRIS Authentication guides for connection information.

To connect to Workday and collect proof, your Workday configuration must meet the following requirements.

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

Authentication type: Custom​

Custom authentication parameters:​

  • Use my credentials (recommended): Username, Password, Web Services Endpoint URL​

  • Use just my OAuth Credentials: Web Services Endpoint URL, Subdomain, Client ID, Client Secret, Token URL, Refresh Token

When you configure a Hypersync for Workday for the first time, you must provide the following information:

Use my credentials (recommended) - If you choose this authentication option, you need the following information:

  • Username

  • Password

  • Web Services Endpoint URL

Use just my OAuth Credentials - If you choose this authentication option, you need the following information:

  • Web Services Endpoint URL

  • Subdomain

  • Client ID

  • Client Secret

  • Token URL

  • Refresh Token

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.

Additional documentation

Connecting to Workday

  1. From the left menu, select either Controls or Labels, depending on the object you want to link to the Hypersync.

  2. Select the control or label for which you want to automate proof.

  3. Select the Automations tab.

  4. Click Create Hypersync.

    The Choose app window opens.

  5. Use the filter at the top of the Choose app window to find 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.

  6. Select your app.

    The Connect window opens.

    Note: Hyperproof uses Merge, a third-party API, to streamline the connection process. For more information on how Hyperproof integrates with Merge, please refer to the Hyperproof Security Overview.

  7. Sign in to your account.

Note: Depending on the app, you might be asked for your username and password or a token. The sign-in process varies by app. See the Requirements and Connection configuration sections of the specific Hypersync document for more details.

Did this answer your question?