Cbox ID
Workday
Workday
Connect Workday and your people are kept in step with it: an account from their start date, deactivated — every session signed out — at the end of their last day, and each department a group your administrators can map to roles.
In Workday
In the portal, open Directory sync, choose Using an HR system?, and pick Workday. Then, in Workday:
- Run the task Create Integration System User. Give it a name such as ISU_CboxID and a strong password, and tick "Do Not Allow UI Sessions".
- Run Create Security Group, choose "Integration System Security Group (Unconstrained)", and add the user. In Maintain Permissions for Security Group, give it Get access to the Worker Data domains your report reads (workers, work email, job details, supervisory organizations), then run Activate Pending Security Policy Changes.
- Create an Advanced custom report on the All Workers data source (so it includes terminated workers), tick "Enable As Web Service", and share it with the integration user.
- Add one column per field and set each column's alias to exactly: Employee_ID, Work_Email, Legal_First_Name, Legal_Last_Name, Preferred_Name, Active_Status, On_Leave, Hire_Date, Termination_Date, Supervisory_Organization_ID, Supervisory_Organization, Manager_Employee_ID, Business_Title. Only Employee_ID and Work_Email are required; a report that already exists can keep its own names and map them here.
- From the report's related actions choose Web Service → View URLs, and copy the JSON URL.
- Paste the URL, the user name as ISU_CboxID@your-tenant, and its password. To use OAuth instead, run Register API Client for Integrations with non-expiring refresh tokens, then Manage Refresh Tokens for Integrations for the integration user, and paste the client ID, secret and refresh token.
What to paste into the portal
| Field | Where it comes from |
|---|---|
| Report web-service URL | The JSON URL from the report's related actions → Web Service → View URLs. |
| Integration system user, optional | The ISU's user name followed by @ and your tenant name. Leave empty when you use an API client instead. |
| Integration system user password, optional (secret) | The ISU's password. |
| API client ID, optional | Only when you use an API client instead of a user name and password. |
| API client secret, optional (secret) | The secret shown when the API client was registered. |
| Refresh token, optional (secret) | From Manage Refresh Tokens for Integrations, issued to the integration system user. |
The portal checks these with Workday before anything is stored, and never shows a secret again.
What happens next
- The first sync starts straight away and runs in the background; the portal shows how it went.
- After that, Workday is read in full about every hour.
- A person whose termination date has passed loses access at the end of that day, even if their status has not been updated yet. People on leave keep their account.
- People who left before the connection was made, and people who have not started yet, get no account.
- A person with no work email, or whose email already belongs to an account that is not linked to this connection, is listed as not synced — by their Workday employee ID — and nobody else is held up.
- If a sync would suddenly deactivate more than half of your people, it deactivates nobody and says why: that is almost always permissions that changed in Workday, not a mass layoff.
Workday's own guide: https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/reports-as-a-service-raas-/dan1370797813643.html.
Related
- Identity provider guides — every provider and HR system the portal guides you through.
- Directory Sync — the portal's directory setup.