Oleria’s Trustfusion platform offers a central place to continuously monitor and manage access for all identities - human, non-human, and AI - across all systems: on-prem, in the cloud, or custom. It provides adaptive and autonomous access security that sets your business free. As part of that promise, we integrate your Workday into the Oleria platform. This document provides step-by-step guidance for integrating Workday with your Oleria workspace.Documentation Index
Fetch the complete documentation index at: https://docs.oleria.com/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- Administrator permission on the Oleria workspace
- Workday admin credentials
Use a service account (and not an employee account) with the suggested privileges for the integration to ensure continuity.
Create an Integration System User in Workday
Create an Integration System User and grant View Only permissions.Create the Integration System User
Log in to Workday. Type Create integration system user in the search window and select the task.The Create Integration System User window opens. Provide the following:
- User Name
- Password
-
Set Session timeout minutes to
0 -
Select the Do Not Allow UI Sessions checkbox

Exempt the user from password expiration
In the search window, type Maintain Password Rules and select the task.Under System Users exempt from password expiration, search and add the Oleria Integration System User.

Create an integration security group
In the search window, type Create security group and select the task.From the Type of Tenanted Security Group dropdown, select Integration System Security Group (Unconstrained) and give it a name, for example, Oleria Integration Security Group.

Add the user to the security group
From the Integration System User field, search and select the Oleria Integration System User created in the previous step.

Add permissions to the security group
In the search window, type Maintain permissions for Security Group and select the task.Search and add the Oleria Integration Security Group in the Source Security Group field. Select Ok.
In Maintain Permissions for Security Group → Domain Security Policy Permissions, add the following permissions:


- (“View Only”, “Integration Event”, “Integration”)
- (“View Only”, “Integration Debug”, “Integration”)
- (“View Only”, “Integration Process”, “Integration”)
- (“View Only”, “Integration Build”, “Integration”)
- (“View Only”, “Worker Data: Workers”, “Staffing”)
- (“View Only”, “Person Data: Personal Data”, “Personal Data”)
- (“View Only”, “Worker Data: Employment Data”, “Staffing”)
- (“View Only”, “Worker Data: Staffing”, “Staffing”)
- (“View Only”, “Worker Data: Public Worker Reports”, “Staffing”)
- (“View Only”, “Worker Data: Organization information”, “Staffing”)
- (“View Only”, “Person Data: Personal information”, “Personal Data”)
- (“View Only”, “Person Data: Name”, “Contact information”)
- (“View Only”, “Person Data: Person Reports”, “Personal Data”)
- (“View Only”, “Worker Data: Service Dates”, “Staffing”)
- (“View Only”, “Worker Data: Current Staffing Information”, “Staffing”)
- (“View Only”, “Person Data: Public Work Email Address Integration”, “Contact information”)
- (“View Only”, “Person Data: Private Work Email Integration”, “Contact information”)
- (“View Only”, “View: Supervisory Organization”, “Organizations and Roles”)
- (“View Only”, “Person Data: Private Home Email Integration”, “Contact information”)
- (‘View Only’, ‘Person Data: Public Home Email Address Integration’, ‘Contact Information’)
- (‘View Only’, ‘Person Data: Home Contact Information’, ‘Contact Information’)
- (‘View Only’, ‘Worker Data: Employee Contracts’, ‘Staffing’)
- (‘View Only’, ‘Worker Data: All Positions’, ‘Staffing’)
- (‘View Only’, ‘National ID Identification’, ‘Personal Data’)
- (‘View Only’, ‘Manage: Supervisory Organization’, ‘Organizations and Roles’)
- (‘View Only’, ‘Indexed Data Source: Workers’, ‘Staffing’)
- (‘View Only’, ‘Reports: Organization’, ‘Organizations and Roles’)
- (‘View Only’, ‘Worker Position: View’, ‘Staffing’)
- (‘View Only’, ‘Person Data: Work Contact Information’, ‘Contact Information’)
- (‘View Only’, ‘Person Data: ID Information’, ‘Personal Data’)
- (‘View Only’, ‘Job Information’, ‘Jobs and Positions’)
- (‘View Only’, ‘Staffing Actions: Additional Job Classifications’, ‘Staffing’)
- (‘View Only’, ‘Staffing Actions: Primary Job’, ‘Staffing’)
- (‘View Only’, ‘Worker Data: Job Family on Worker Profile’, ‘Staffing’)
- (‘View Only’, ‘Worker Data: Directory’, ‘People Experience’)
- (‘View Only’, ‘Worker Data: General Staffing Information’, ‘Staffing’)
- (‘View Only’, ‘Worker Data: Job Details’, ‘Staffing’)
- (‘Get Only’, ‘Worker Data Current Job Profile Information’, ‘Staffing’)
- (‘View Only’, ‘Worker Data: Active and Terminated Workers’, ‘Staffing’)
- (‘View Only’, ‘Worker Data: Business Title on Worker Profile’, ‘Staffing’)
- (‘View Only’, ‘Worker Data: Current Job Profile Information’, ‘Staffing’)
- (‘View Only’, ‘Staffing Actions: Job Profile’, ‘Jobs & Positions’)
- (‘View Only’, ‘Job Profile: View’, ‘Integration’)
- (‘Get Only’, ‘Integration Event’, ‘Integration’)
- (‘Get Only’, ‘Integration Build’, ‘Integration’)
- (‘Get Only’, ‘Integration Process’, ‘Integration’)
- (‘Get Only’, ‘Integration Debug’, ‘Integration’)
- (‘Get Only’, ‘Worker Data: Organization Information’, ‘Staffing’)
- (‘Get Only’, ‘Worker Data: Public Worker Reports’, ‘Staffing’)
- (‘Get Only’, ‘Worker Data: Current Staffing Information’, ‘Staffing’)
Activate pending security policy changes
Type Activate Pending Security Policy Changes in the search window and select the task.Provide a comment and select OK.
On the next screen, select the Confirm checkbox and select OK.


Register a new API client
Type Register API Client for integrations in the search window and select the task.
- Enter a name for your API client in the Client Name field.
- Unselect the Non-Expiring Refresh tokens checkbox.
- Add 180 in the Refresh Token Timeout (in days) field.
-
Search and add the following scopes in the Scope (Functional Areas) field:
- Integration
- Jobs & Positions
- Organizations and Roles
- Personal Data
- Public Data
- Staffing
- Tenant Non-Configurable
- Worker Profile and Skills
- Contact Information
-
Select the Include Workday Owned Scope checkbox.


Generate a refresh token
Type View API Clients in the search window and select the task.Select API Client for Integrations.
Select the API client registered in the previous step.Select the ellipsis → API client → Manage Refresh Tokens for Integrations.
Search and select the Oleria Integration System User created above. Select Ok.
The Delete or Regenerate Refresh Token dialog opens. Select the Generate New Refresh Token checkbox.




Connect Workday to Oleria
Open the integration and provide credentials
Go to your Oleria workspace, select Integrations → select Workday, and provide the following:
-
Host Name - your Workday home URL
- To find it: log in to Workday, search for View API clients, and the Workday REST API endpoint will be visible at the top of the page
- Tenant ID - select your account and the organization ID
- Client ID - captured in the previous section
- Client Secret - captured in the previous section
- Refresh Token - captured in the previous section
-
Refresh Token Expiry (optional) - leave empty if a non-expiring refresh token was set up


Confirm the connection
Find the newly integrated Workday instance in your Oleria workspace connected integrations.

