Aller au contenu principal

Guide pratique

Workday Tenant Access

How to understand tenants, environments, security groups, and authentication so that the right people reach the right data in Workday, and only the right people.

A Workday tenant is a dedicated instance of the platform that holds an organisation's configuration, data, and security setup. Access to that tenant is controlled by a layered model of security groups, roles, and domain policies. Getting tenant access right matters as much as getting the configuration right: an elegant build that is open to everyone, or locked to the wrong people, fails the business just the same.

Understanding the tenant landscape

Most organisations work with several tenants rather than one. An implementation tenant is used during the project to build and test configuration. A sandbox tenant gives teams a safe place to try changes and integrations without touching live data. A preview tenant lets the organisation see upcoming Workday updates before they reach production. The production tenant is the live environment that employees, managers, and administrators use every day.

Keeping these environments separate is essential. Test data must never leak into production, and production access must be granted far more carefully than access to a sandbox.

How access is granted

Workday does not assign permissions to individuals directly. Instead, a person is placed into one or more security groups, and each group carries roles and domain permissions. A role such as manager or administrator defines what a user can do, while a domain security policy defines which data the user can see. The two must line up: a role without the right domain access is useless, and domain access without a matching role is dangerous.

Design the security model around responsibilities, not around individuals. When a person changes job, moving them between groups should be a routine action, not a redesign.

Authentication and single sign on

Most organisations connect Workday to their identity provider so that users sign in with their corporate credentials. This single sign on pattern reduces the number of passwords in circulation and lets the identity team disable access in one place when someone leaves. Multi factor authentication should be enforced for administrators and for any access from outside the corporate network. Where single sign on is not yet available, a strong password policy and regular review are the minimum.

Integration system users

Integrations need their own identity. A dedicated integration system user, placed in a tightly scoped security group, should perform each automated exchange. Never let an integration run under a real person's account: when that person leaves, the integration breaks, and the audit trail points at the wrong identity. Grant integration users only the domains they truly need, and rotate their credentials on a schedule.

Provisioning and deprovisioning

Access should follow a documented path. A new starter receives a standard set of groups based on role; a mover is reviewed before groups change; a leaver is disabled promptly across every tenant, not only production. Joiner, mover, and leaver processes are the backbone of tenant hygiene, and they work best when they are automated from the human resources record rather than handled by email.

Reviews and governance

Regular access reviews catch the slow drift that accumulates in any system. Review privileged groups most often, confirm that each member still needs the access, and record the decision. Keep a named owner for each tenant, a clear approval route for new security groups, and a log of who changed what. Governance is what turns a working security model into a trustworthy one.

Best practices

  • Start from the principle of least privilege and widen only when a real need is shown.
  • Separate production access from sandbox access and require a stronger approval for production.
  • Give every integration its own system user with narrowly scoped domains.
  • Automate joiner, mover, and leaver changes from the source of record.
  • Review privileged groups on a fixed calendar and keep the evidence.
  • Test access changes in a non production tenant before applying them live.

Common pitfalls

The most frequent problems are familiar. Administrators accumulate permanent broad access because removing it feels risky. Integrations run under personal accounts. Sandbox credentials are shared across a team. Former employees keep access because no one owns the leaver step. Each of these is avoidable with a little discipline and a clear owner.

Getting started

Begin by mapping the tenants in use and the purpose of each one. Then document the security groups, who approves membership, and which domains each group can reach. Finally, agree the joiner, mover, and leaver process and the review calendar. With that foundation in place, Workday tenant access becomes predictable, auditable, and safe to change.