Skip to main content
Oregon Small Schools Initiative A program of E3
Reference

Workday tenant access

A tenant is one organisation's private corner of Workday. Everything about how people sign in, what they can see, and what they can change is shaped by how that tenant's access is set up and kept under control.

What a tenant is

In cloud software, a tenant is a dedicated instance of the product that holds one customer's data and configuration. Your Workday tenant is separate from every other organisation's, which means your people records, payroll and reports live in their own space and are not mixed with anyone else's. Access to that tenant is the doorway through which employees, managers and administrators reach the system.

How access is granted

Getting into a Workday tenant usually begins with a user account tied to one person. From there, access is shaped by a few layers that work together. A person signs in through an authentication method, often single sign on through the organisation's own identity system. What they can do after signing in is then determined by the security groups and roles assigned to their account, which map out exactly which screens, tasks and data they can reach.

The types of access

  • Employee self service. The everyday access that lets a person view their own pay, update their details, request time off and complete tasks assigned to them.
  • Manager access. The wider view that lets a manager see their team, approve requests, and run reports about the people they lead.
  • Administrator access. The highest level, held by the people who configure the tenant, manage security groups and set up integrations.
  • System access. The credentials used by connected applications and integrations, which exchange data without a person at the keyboard.

Keeping access protected

Because a tenant holds sensitive information about people, organisations treat its access as something to review, not something to set once and forget. The strongest habits are familiar ones. Give each account only the access its role actually needs. Require a second form of proof for administrative sign in. Remove access promptly when someone changes role or leaves. And revisit security groups on a regular schedule so that old permissions do not quietly pile up.

Common access questions

Support teams field the same access questions again and again. A new hire needs an account set up before their first day. An employee forgets their password and needs a reset. A manager cannot see a report they believe they should. An administrator needs to know who changed a setting and when. Answering each one well comes back to the same basics: knowing how accounts are created, how roles are assigned, and how to trace what a person can and cannot see.

Return to the main site

This reference page sits alongside the rest of the site. Return to the home page, or get in contact with a question.