The Workday security hierarchy is the layered model that determines who can see or change data inside a tenant. It combines tenant, organization, position, security group, domain, business process, and access level controls so access can be scoped to business structure and job responsibility.
What the Workday security hierarchy does
The Workday security hierarchy is not a single control, but a layered decision model for access. It determines whether a person or process can view, update, or act on data by combining tenant-wide settings with organization, position, security group, domain, business process, and access level rules. The result is access that can follow business structure rather than being granted globally.
That structure matters because Workday security is designed around business context. A user may be allowed to see one set of records because of their role, reporting line, or assigned organization, while being blocked from another even inside the same tenant. In practice, the hierarchy prevents a flat permission model from exposing every object to every authorized user.
How the hierarchy layers access decisions
Think of the hierarchy as multiple filters applied in sequence. Tenant controls set the outer boundary, while organization and position rules narrow visibility based on where a user sits in the workforce model. Security groups then collect users who share an access pattern, and domains and business process policies decide what those users can actually read or change.
Access levels add another layer by shaping the depth of access within a secured area. For example, a user may be allowed to initiate or approve a business process but not alter the underlying data, or may be able to view a record without editing it. This layered model is what makes Workday security expressive enough to reflect separation of duties, delegated administration, and job-based access.
Why Workday uses hierarchy instead of flat roles
Workday’s hierarchy is built to mirror operating structure, not just job titles. That reduces the need to assign broad permissions manually and makes access more adaptable when people move teams, change positions, or inherit responsibilities through organizational changes. It also helps avoid overexposure when the same tenant holds HR, finance, payroll, and operational data.
The trade-off is complexity. Security outcomes can change when an organization assignment, domain policy, or business process rule is adjusted, even if the user’s apparent role has not changed. For that reason, the hierarchy is best understood as a policy engine with multiple dependencies rather than a simple list of permissions.
Common security implications and failure modes
Misconfiguration is the main risk. A security group that is too broad, a domain policy that grants more than intended, or an access level that allows editing instead of view-only access can expose sensitive records across employee, payroll, or manager workflows. Because Workday access often reflects business relationships, mistakes can scale quickly across organizational changes.
Another failure mode is stale or inherited access. Users may retain access after role changes if the hierarchy is not reviewed carefully, especially where business process permissions and domain security overlap. That is why the model needs periodic review, not just initial setup, and why changes to structure should be treated as security-relevant events.
Risk and Threat Considerations
Workday security hierarchy failures can expose highly sensitive HR and finance data, or allow unauthorized changes to business processes that affect hiring, pay, approvals, or reporting. The risk is often not a single broken permission, but an overly permissive combination of hierarchy layers that creates unintended access paths.
Failure mechanism: A broad security group, overly generous domain access, or mis-scoped business process policy can combine to grant visibility or action rights beyond the intended organization or job boundary. Because Workday access is layered, a small policy error can create a larger effective exposure than the individual rule suggests.
Impact: Unauthorized disclosure, approval abuse, payroll or employee-data manipulation, and weak segregation of duties can follow. The same issue can also complicate audits, because the effective access path is distributed across several policy layers rather than visible in one place.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 provides the primary governance reference for this term.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | Workday hierarchy governs who receives scoped access and how it is managed over time. |
| AC-6 — Least Privilege | The hierarchy should limit each user to the minimum access their role and organization require. | |
| AC-5 — Separation of Duties | Workday business process and domain layers can enforce distinct approval and edit paths. | |
| Recommendation — Scope account access to job and organizational need, then review it when roles or structures change. Apply least privilege so Workday access is limited by business need, not convenience. Separate initiate, approve, and edit permissions to reduce abuse of Workday workflows. | ||
Practitioner Guidance
Why practitioners should care: The main governance challenge is not whether Workday has security controls, but whether the hierarchy reflects current business reality. Ownership should be clear for tenant-level settings, security groups, domain policies, and business process security, because each layer can change the effective access outcome.
What to watch for: Review access after org restructures, position changes, acquisitions, and business process redesigns, since those are the moments when hierarchy-driven access drift most often appears. A useful reference for understanding the broader Workday model is the Workday Security Guide, which covers security groups, domain and business process policies, and tenant logging.
For integration-heavy environments, also pay close attention to non-human access paths such as integration users and API clients, because those controls often sit alongside the same hierarchy and can bypass the assumptions people make about human roles. The Workday Integration System Users Guide is the most direct companion for that operational side of Workday security.
Related resources from NHI Mgmt Group
- How should security teams govern hierarchy-based access in multi-tenant applications?
- How should security teams control AI agent access to Workday in enterprise environments?
- How should security teams align HR and IAM processes when integrating Workday with an identity governance platform?
- How should HR teams evaluate eSignature integrations for Workday when cost, automation, and security all matter?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org