Home/Workday Tenant Access
Workday Tenant Access
A practical guide to getting the right people into the right Workday tenant, with the right permissions, at the right time.
Workday is delivered as a cloud service, and every organisation that uses it works inside its own tenant. A tenant is the isolated space that holds your data, configuration, business processes and user accounts. Tenant access is the set of rules and routines that decide who can sign in to that space, what they can see once they are there, and how quickly access is granted or removed as people join, move and leave.
Access is easy to take for granted when it works. When it does not, the effects are immediate: a new starter cannot complete onboarding, a manager cannot approve a leave request, an analyst cannot open the report that leadership is waiting for. Because Workday often holds sensitive personal and financial information, a loose approach to access is also a security and audit risk. Getting it right is as much about governance as it is about technical setup.
Why tenant access matters
Tenant access sits at the meeting point of security, compliance and everyday productivity. A well managed model delivers several outcomes at once:
- People can start work on their first day instead of waiting days for an account.
- Users see only the data and tasks their role requires, which supports the principle of least privilege.
- Joiners, movers and leavers are handled consistently, so old access does not accumulate.
- Audits are easier, because requests, approvals and reviews leave a clear trail.
- Support teams spend less time on avoidable password and permission tickets.
Understanding tenant types
Most organisations work with more than one tenant. Separating them keeps testing away from live data and gives teams a safe place to learn. The table below describes the three types you will usually meet.
| Tenant type | Purpose | Who should have access |
|---|---|---|
| Implementation | Building and configuring the platform before it goes live | Implementation team, functional leads and approved testers |
| Sandbox or preview | Testing configuration changes, integrations and new releases | Administrators, analysts and integration teams |
| Production | Live business operations and real employee and finance data | Active staff, managers and support roles only |
A common mistake is to treat the implementation tenant as a permanent playground. Over time it fills with stale accounts and loose permissions, which creates confusion and risk. Each tenant should have a named owner, a stated purpose and a defined group of authorised users.
Access roles and security groups
Workday does not usually grant access person by person. Instead, users are placed into security groups, and those groups carry permissions. Training people to think in groups rather than individual rights keeps the model understandable and auditable.
- Employee as self covers the basic ability to view and update a person's own information and complete self service tasks.
- Manager roles add team views, approvals and people processes on top of the self service basics.
- Functional administrators hold the configuration and maintenance rights for a domain such as HR, payroll or finance.
- Report writers and analysts need access to reporting tools, data sources and the underlying security model.
- Integration and technical users require system accounts for interfaces, data loads and monitoring.
- Security administrators manage the groups themselves, so this role should be small and carefully reviewed.
Where possible, map these roles to the identity information your organisation already holds, such as department, job family and manager. That makes access predictable and reduces the number of manual exceptions.
Requesting access
A clear request process protects both the user and the organisation. A dependable flow looks like this:
- Identify the need. The user or their manager states the role and the tasks they must perform in Workday.
- Select the group. The request maps the role to an existing security group rather than inventing new permissions.
- Approve. The line manager confirms the business need, and the tenant owner or security administrator approves the group.
- Provision. Access is granted in the correct tenant and the user is told how to sign in.
- Record. The request, approver and group are logged so the decision can be reviewed later.
Keep the steps short enough that people actually follow them. A request that takes a week will be bypassed with shared logins and informal workarounds, which is exactly what good access management is trying to prevent.
Signing in with single sign on
Many organisations connect Workday to their identity provider so that users sign in with their normal corporate credentials. This is often described as single sign on, and it brings real benefits: fewer passwords to remember, faster onboarding and a single place to disable an account when someone leaves.
Two points are worth planning for. First, the identity provider must be configured to release the right attributes so that Workday can match the user to the correct person record. Second, multi factor authentication should be enabled for administrative roles, because those accounts can change configuration and expose sensitive data.
Some tenants, particularly implementation and sandbox environments, may allow local sign in for approved testers or integration accounts. Those exceptions should be few, documented and reviewed, not the default.
Managing access over time
Access is not a one off task. People join, change roles and leave, and each event should trigger a matching change in Workday.
- Joiners. Access is requested before the start date so the person can complete onboarding on day one.
- Movers. A change of role should add the new groups and remove the old ones. Simply adding permissions lets access accumulate.
- Leavers. Accounts are disabled promptly, and any system or integration accounts owned by that person are reassigned.
- Contractors. Time limited access is set to expire automatically wherever the platform allows it.
- Reviews. A regular review confirms that group membership still matches the current role, with a focus on administrative and integration rights.
Automating these events through your identity provider reduces delay and error. Where automation is not yet possible, a simple checklist and a named owner are far better than an informal understanding.
Common access problems
The user cannot sign in
Confirm that the account exists, that it is enabled, and that the person is using the correct tenant and sign in route. If single sign on is in use, check the identity provider first, since most failures begin there rather than in Workday.
The user can sign in but sees nothing
This usually means the account is valid but has not been placed in the right security groups, or the group applies to a different organisation or supervisory scope. Check the group assignment before creating new permissions.
The user can see too much
Review group membership and any role based assignments for data scope. Excess access is a security issue, not a convenience, and should be corrected promptly.
A test account has production rights
Test and integration accounts should be limited to the tenants they need. If an account carries rights into production, treat it as a finding and resolve it before the next review.
Best practices
- Name a tenant owner. Every tenant needs a clear owner who is accountable for who gets in and why.
- Use groups, not exceptions. Grant access through security groups so the model stays consistent and reviewable.
- Apply least privilege. Give the smallest set of permissions that lets a person do their job.
- Automate joiners and leavers. Connect access to the identity source rather than relying on email requests.
- Protect admin access. Require multi factor authentication and keep the number of security administrators small.
- Review regularly. Schedule access reviews and act on the findings instead of filing them away.
- Document the route. Publish how to request access, who approves it and how to get help.
- Separate duties. Avoid letting one person both request and approve sensitive access.
Measuring access hygiene
Access management improves when it is measured. Useful indicators include the time from request to provision, the number of accounts without a matching active employee, the proportion of administrative accounts using multi factor authentication, and the number of review findings still open. Tracking these over time shows whether the process is actually working.
Frequently asked questions
What is a Workday tenant?
A tenant is an isolated instance of Workday that holds one organisation's data, configuration and users. Organisations often keep separate tenants for implementation, testing and live operations.
Who should approve access?
The line manager should confirm the business need, and the tenant owner or security administrator should approve the group. Sensitive or administrative access benefits from a second approver.
Should everyone use single sign on?
For most staff it is the simplest and safest option. Limited local accounts may still be needed for approved testers and integration users, but these should be documented and reviewed.
How often should access be reviewed?
Many organisations review standard access annually and administrative access more often. Reviews should also be triggered by major role changes or audit requirements.
What happens to access when someone leaves?
Their account should be disabled promptly, and any system or integration accounts they owned should be reassigned. Automating this through the identity provider is the most reliable approach.
Bringing it together
Workday tenant access works best when it is treated as a governed process rather than a series of one off favours. Clear tenant ownership, group based permissions, a short request route, automated joiner and leaver handling and regular reviews together keep the platform secure and usable. The result is that people can do their work without waiting, and the organisation can show that access is controlled and justified.
To build the skills that sit on top of access, read our guide to Workday Business Application Training.