Check which workforce data a connection can read

Compare who can manage a workforce connection with the people and fields it can read. Check the result against fictional records.

Before you start

  • Use a test tenant, fictional employee records and an administrator who can restore the starting permissions. Use a sample with harmless fields and leave real employee identifiers, credentials and raw responses out of your notes.
  • Pick an included and an excluded test field or record. Use the same test request or view before and after changing an assignment.

Data and access

Shared or checked
The workforce connection can read the test employee records and fields allowed by its configured access. Compare what it returns with the approved field list.
Check separately
The ability to administer a connection and the connection’s permissions to read employee data are separate.
  1. Rippling

    Review the permission profile that provides access to people data. Compare an explicit field grant with the default profile and the minimum directory fields. Test a non-default fictional field with the intended profile assignee. Check for temporary elevated access if the account manages hiring or offboarding.

    Check. The exact test profile shows the expected field grant. Record what the assignee can read and account for any temporary grant before attributing the result.

  2. HiBob

    In Bob, verify which permission group belongs to the test API service user. Check both People’s fields and whose records the group applies to. Read an allowed field for the included test employee and compare it with the result for a fictional employee outside the group’s scope.

    Check. The service user receives the allowed field for the included employee. Record a denied or omitted result for the out-of-scope person.

  3. ADP

    In a Workforce Now API Central test project, check who can manage projects, certificates and member roles. With the approved test project connection, make a supported read against test data. Compare the result with the API access approved for the project. Record console role permissions separately from what the connection returns.

    Check. The supported test read returns only data in the approved project scope. Record who can manage the project separately.

  4. Record the visible boundary

    Record whether the selected field was returned, omitted or denied and which test account or service user made the request. Restore the test assignment and repeat the original check.

    Check. The restored assignment reproduces the original field and record results for the same test identity.

Check your result

The permitted test record is readable and the restricted field or person stays outside the intended access. The record identifies the account that can change the connection and the identity that actually reads data.

How to verify your setup

If you get stuck

A field is visible that you expected to be restricted

Review the default profile, record scope and other grants for the exact account that made the request. Recheck which provider project or service user the client is using.

Report a problem with this guide

Explore all setup guides →