Beta: The Workday Learning Integration is currently available as a beta feature. Your feedback helps shape future improvements and capabilities. If you have questions, ideas, or need assistance, contact your Customer Success Manager or lms-support@honehq.com.
💡 Before you begin
Watch our step-by-step setup walkthrough before getting started:
Overview
The Workday Learning Integration publishes supported Hone learning content to Workday Learning and reports learner enrollment and completion data back to Workday. Administrators manage learning content in Hone, while learners discover and launch Hone learning from within their Workday Learning experience.
Setting up the integration requires access to both Hone and Workday. The process consists of four steps:
Create an Integration System User (ISU) and Integration System Security Group (ISSG), and configure the required Workday security.
- Start the integration setup in Hone.
- Create a Workday API Client.
- Complete the configuration and connect the integration.
Step 1: Create the Integration System User and Security Group
Hone authenticates to Workday using a dedicated Integration System User (ISU). The ISU should be assigned to an Integration System Security Group (Unconstrained) (ISSG) that grants only the permissions required by the Hone integration.
1. Create the Integration System User
In Workday:
- Run the Create Integration System User task.
- Create a dedicated user for the Hone integration.
- Record the ISU username for your Workday configuration.
- Configure the ISU according to your organization's integration-user policies, including any password expiration or session restrictions required by your organization.
The ISU should be used only by the Hone integration.
2. Create an Integration System Security Group
Create a dedicated Integration System Security Group (Unconstrained) for Hone and assign the Hone ISU as a member.
For example:
- Security Group Type: Integration System Security Group (Unconstrained)
- Security Group Name: Hone Integration
Using a dedicated ISSG makes it easier to review and maintain the integration's Workday permissions independently from other integrations.
3. Configure Domain Security Policy Permissions
Add the Hone ISSG to the following Workday domain security policies.
| Domain Security Policy | Required Integration Permission |
|---|---|
| Worker Data: Public Worker Reports | Get Only |
| View External Learning User | Get, Put |
| Manage: Learning Course Enrollments | Get, Put |
| Maintain Archived External Learning User | Get, Put |
| Manage: Learning Content | Get, Put |
| Manage: Create and Edit Learning Roles | Get, Put |
| Set Up: Learning Catalog | Get, Put |
| Learning Access | Get, Put |
For Learning Core → Manage: Learning Content, confirm that the Hone ISSG has both:
- Report/Task Permissions: View, Modify
- Integration Permissions: Get, Put
These permissions allow Hone to read the worker information required for learner matching and to create or update supported Workday Learning records such as learning users, instructors, topics, courses, course offerings, programs, and enrollments.
4. Configure Business Process Security
Several Workday Learning web services initiate Workday business processes. For each business process below, add the Hone ISSG to the applicable Initiate web-service action in the business process security policy.
| Business Process | Required Web Service Access | Used for |
|---|---|---|
| Manage Course | Applicable web service initiation action | Creating and updating Hone digital and blended courses |
| Manage Course Offering | Applicable web service initiation action | Creating and updating scheduled course offerings |
| Manage Learning Program | Applicable web service initiation action | Creating and updating Hone learning programs |
| Manage External Learning User | Manage External Learning User (Web Service) | Creating and updating external learning users |
| Manage Learning Instructor | Manage External Learning Instructor (Web Service) | Creating and updating external learning instructors |
Your Workday administrator should confirm that the Hone ISSG appears on the applicable web-service initiation step or action for each business process.
Important: Domain security and business process security are separate. Granting the domain permissions alone may allow Hone to access the underlying Learning objects but still prevent the ISU from initiating operations such as creating courses, offerings, programs, external users, or instructors.
5. Activate the Security Changes
After adding or modifying domain security policies, run:
Activate Pending Security Policy Changes
Review the pending changes, add any required comments, and activate them before testing the Hone integration.
If this step is skipped, newly assigned domain permissions may not yet be available to the Hone ISU.
Step 2: Start the Integration in Hone
Before creating the Workday API Client, begin the setup flow in Hone.
- Navigate to Account Settings > Integrations > LMS.
- Select Workday.
- In the Authentication step, select Generate files to download the Hone OAuth certificate bundle.
- Leave this page open while completing the next step in Workday.
Note: The downloaded ZIP contains Hone's public key and public certificate. In the next step, you'll upload the public certificate to your Workday API Client so Workday can validate JWT Bearer authentication requests from Hone.
Step 3: Create a Workday API Client
In Workday, create a new API Client for the Hone integration.
Configure the client using the following settings.
| Setting | Value |
|---|---|
| Access Token Type | Bearer |
| Allow Integration Messages | Leave unchecked |
| Non-Expiring Refresh Tokens | Leave unchecked |
| Grant Administrative Consent | Leave unchecked |
| Disabled | Leave unchecked |
| Scope (Functional Areas) | Contact Information, Implementation, Learning Core, Staffing |
| Include Workday Owned Scope | Leave unchecked |
| Locked Out due to Excessive Failed Signon Attempts | Leave at the default value |
After creating the API Client, record the following values:
- Client ID
- Client Secret
- Token URL
- Service Host
These values will be entered into Hone during the next step.
Step 4: Connect the Integration
Return to Hone and enter the Workday API Client details.
| Hone Field | Workday Value |
|---|---|
| Service Host | Service Host |
| Token URL | Token URL |
| Client ID | Client ID |
| Client Secret | Client Secret |
Click Test Connection to verify Hone can successfully authenticate with your Workday tenant.
If the connection succeeds, click Connect.
Hone will begin publishing supported learning content to Workday Learning. Depending on the amount of content being published, the initial publication may take several minutes. Progress can be monitored from the integration page.
Once setup is complete, Hone will automatically publish supported content updates and synchronize learner enrollments and completions with Workday Learning.
Troubleshooting
If the connection test fails:
- Verify the Client ID and Client Secret were entered correctly.
- Confirm the Token URL and Service Host match your Workday tenant.
- Verify the API Client includes the required functional area scopes:
- Contact Information
- Implementation
- Learning Core
- Staffing
- Confirm the Integration System User has access to the required Workday Learning and Worker APIs.
If you continue to experience issues, contact lms-support@honehq.com.
Comments
0 comments
Please sign in to leave a comment.