Platform: Workday and Workday Adaptive Planning with single sign-on
Scope: user access requests for department budgeting and workforce planning
The business problem
Access requests kept coming back. A user could not open the planning system, or could open it and not see the department budget. Each case was handled by adding more access, and some users ended up with more access than they needed while the original problem remained.
Existing architecture
In this implementation, access depended on multiple layers: Workday sign-on/user synchronisation, the Workday Adaptive Planning user record, permissions, level ownership, planning groups and a cost-centre-related association. These are an example security design, not a universal six-layer Workday architecture.
Why it happened
The layers were being treated as one. A login error was answered with more level or cost centre access, which cannot fix a sign-on problem. A missing budget was answered with associations, when the user group was the gap.
Design decision
We wrote a runbook with one rule: identify which layer is failing before changing anything. We did not redesign the security model.
Implementation approach
- The user cannot launch the system or gets a login error: check the Workday security group, user sync and the user record. Do not add data access.
- The user logs in and cannot see the department budget: check the permission set, level ownership and user groups, in that order.
- The user sees budgets and cannot reach costing allocations: check the cost centre association.
- The user replaces someone: compare all layers with the earlier user, then apply only what the request covers.
For association uploads, the runbook allows the update and append option. It rules out the replace option, which can erase a user’s existing access.
Controls and validation
A case closes only after the user signs out, signs back in through Workday and confirms the requested function works. The ability to log in is not enough.
Outcome
The diagnostic runbook helped distinguish a missing planning group from a sign-on-path issue in two reviewed cases. It avoided unnecessary data-access expansion and required user confirmation after reauthentication.
Lessons learned
- More access does not fix a sign-on error.
- A reference user helps, and still needs a check against the request. Do not copy everything.
- A permission set that allows salary detail and a read-only user group can sit on the same user. They control different things.
Scope of the outcome
Diagnostic runbook applied to two access requests; not a universal Workday security design.
EPMLogic | Implementation insight based on an anonymized scenario. Exact operational amounts and client details are intentionally omitted.