Skip to main content
Acuity Solutions Corporation

Workday Tenant Access

A practical overview of how teams obtain and govern access to Workday tenants across implementation, testing and production.

What tenant access covers

Workday runs each customer's environment in a tenant. Access to that tenant decides what a person can see, configure and change, so tenant access sits at the meeting point of security, audit and change control. It is not only an administrative task for the IT team. It is part of how an organization protects its data and keeps its configuration predictable.

Good tenant access starts with a simple question: what does this person need to do, in which tenant, and for how long? Every request, role assignment and review should be traceable back to an answer to that question.

Tenant types and their purpose

A Workday customer commonly works with more than one tenant across the life of a project. Each one has a purpose, and access should match that purpose rather than being copied across every environment.

The implementation tenant is where configuration is built and tested during a project. A sandbox tenant supports testing of configuration, security and integrations before a change moves forward. A preview tenant reflects an upcoming release so that teams can assess the impact of new features. The production tenant is the live environment that runs the business day to day.

Broad access in production is rarely justified. Teams that build in an implementation tenant and test in a sandbox can keep production access narrow and well understood.

Requesting access

Access is usually requested through a defined process owned by the Workday administrator or the security team. A strong request records four things: the business reason, the role or security group required, the tenant involved, and the period for which access is needed.

Approvals should come from someone who understands the work as well as someone who owns the risk. Short lived access for a specific task is easier to govern than a permanent assignment that nobody revisits.

Security roles and least privilege

Workday security is built from roles and groups, and the way those are combined decides what a user can reach. The guiding principle is least privilege: grant the smallest set of permissions that lets a person complete the task, and avoid handing out broad administrator roles when a focused role will do.

Separation of duties matters as much as the size of a permission. The person who configures a change should not always be the person who approves it or moves it to production. Where duties are separated, a mistake or a misuse of access is far more likely to be noticed before it spreads.

Sign in and session control

Most organizations connect Workday to their identity provider so that people sign in with single sign on. That connection should be paired with multi factor authentication, sensible session timeouts and a clear process for removing access when a person changes role or leaves the organization.

Shared logins weaken every other control. Where a shared or service account is genuinely required, treat it as a privileged account, restrict who can use it, and keep a record of its purpose. Our perspective on managing service accounts and secrets covers how that kind of account can be protected.

Access reviews and offboarding

Access that is never reviewed slowly drifts away from the work it was meant to support. A regular review compares current assignments with current roles, confirms that each assignment is still needed, and removes what is not. Reviews are easier when access is tied to a named person and a clear reason from the start.

Offboarding deserves its own checklist. When a person leaves, or moves to a different team, their tenant access should be removed or reduced on the same day as the change. Integrations and service accounts connected to that person should be reviewed at the same time, because they are easy to overlook.

A practical checklist

Before you approve the next request, confirm the following points.

  • The request names the tenant, the role and the business reason.
  • Access is granted for a defined period and not left open by default.
  • The role reflects the task and does not include unrelated permissions.
  • Duties are separated where the risk of a change requires it.
  • Single sign on and multi factor authentication are in use.
  • A named owner reviews the assignment on a regular schedule.
  • Offboarding removes access and reviews any linked account.