UKG Pro WFM: require manager-level integration user for time-off#395
Open
jerann wants to merge 1 commit into
Open
UKG Pro WFM: require manager-level integration user for time-off#395jerann wants to merge 1 commit into
jerann wants to merge 1 commit into
Conversation
Time-off create moves to the manager endpoint, which checks manager scope. Update the credential step to require a dedicated integration user with manager-level permissions (FAP, Manager Role + Hyperfind, data access) and add a Note that exact names are tenant-specific. INT-8679
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the UKG Pro Workforce Management connection guide to clarify that the integration must use a dedicated, manager-permissioned user for time-off management, aligning the documentation with the connector’s move to the manager time-off endpoint.
Changes:
- Updates the credential preparation step to require a dedicated integration user with manager-level permissions.
- Adds guidance on required UKG role/profile/scope setup (Function Access Profile, Manager Role/employee group scope, and data access).
- Adds a note clarifying that exact role/profile/access labels are tenant/version specific.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| Grant the integration user: | ||
|
|
||
| - A manager Function Access Profile that allows managing employee time-off requests (create and edit). | ||
| - A Manager Role with an employee group (Hyperfind) covering every employee you want to manage time-off for. Employees outside this scope are rejected. |
| If time-off requests should be approved automatically instead of left pending, enable Auto Approval on the relevant time-off request subtype. | ||
|
|
||
| <Note> | ||
| The exact profile, role, and access-point names vary by UKG tenant and version. Ask your UKG admin to grant the integration user manager-level time-off permissions covering the employees in scope. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Updates the UKG Pro WFM connection guide credential step to require a dedicated integration user with manager-level permissions, and adds a
<Note>that exact profile/role/access-point names are tenant-specific.Why
The UKG Pro WFM time-off
createin the connector is moving from the employee self-service endpoint (POST /v1/scheduling/employee_timeoff) to the manager endpoint (POST /v1/scheduling/timeoff), so requests are created for the target employee instead of as the connected service user. The manager endpoint checks manager scope, so a plain integration user fails against it. The guide previously listed only credential fields and never stated the required permissions, so customers following it as-is would still hit a permission failure after the connector fix ships.Scope
Ticket: INT-8679