Workday Tenant Access
Workday is organised into tenants, and each tenant is its own secure space for a single customer. Tenant access is the set of controls that decides who can sign in, what they can see, and what they can change once they are inside.
What a Workday tenant is
A Workday tenant is a single, dedicated instance of the Workday platform owned by one organisation. Each tenant holds that organisation's own data, configuration, and security settings, kept separate from every other customer. When a team talks about logging in to Workday, they usually mean signing in to their own tenant.
How tenant access works
Access begins with a user account. Every account is tied to a person and matched to a set of roles that decide what that person can do. Workday checks a user's credentials when they sign in, then applies the security attached to their roles for the rest of the session. Many tenants also connect an identity provider so staff sign in through the same single sign on system they already use.
Roles and security groups
Rather than assigning permissions one person at a time, Workday groups people into roles and security groups. A role such as Human Resources Administrator or Manager brings a collection of tasks, while security groups control access to specific data. This keeps permission changes consistent because updating a group updates everyone in it.
Types of tenant access
- Administrator access. Full control over configuration, security, and setup.
- Manager self service. Lets managers view and act on their own team.
- Employee self service. Lets staff update their own details and run personal reports.
- Integrator access. A dedicated account for connected systems and tools.
Why controlled tenant access matters
Workday holds sensitive information across finance and people teams, so access has to be deliberate. Strong controls reduce the chance of data leaking through shared or overly broad accounts, and they make it possible to trace an action back to a person and a time. They also keep the tenant stable by limiting who can change core configuration.
Best practices for tenant access
- Give each person their own account rather than sharing a single login.
- Follow the least privilege principle so users hold only the access their role needs.
- Review roles and security groups on a regular schedule and remove access that is no longer needed.
- Connect a single sign on identity provider where possible to centralise sign in and offboarding.
- Use a dedicated integrator account for any connected system instead of a personal account.
Getting started
New tenants usually begin with a small group of administrator accounts, then add manager and employee self service as the rollout grows. Start by listing who needs access and what each group should be able to do, then build roles and security groups to match that list. Regular reviews keep access aligned as teams and responsibilities change.