Skip to content
Machine Learning SalonFree learning resources

Workday

Workday Tenant Access

How tenants are organised, how access is granted by role, and how to keep it clean and auditable.

Workday

What a Workday tenant actually is

In Workday, a tenant is a separate instance of the system with its own data, configuration and security. Each tenant is isolated from the others, so a change made in one does not affect another. Most organisations run several tenants side by side, one for building and testing and one for live business.

Understanding the tenant you are working in is the first step to safe access. The same person can hold different roles in different tenants, and the access that is right for a test tenant is rarely right for the tenant that runs payroll.

Workday tenants kept separate for building, testing and live business
Separate tenants keep building, testing and live business apart.

The essentials

The tenants you will meet

Most Workday landscapes follow the same pattern. Knowing the purpose of each tenant makes access decisions much simpler.

Implementation tenant

The tenant where configuration is built and changed. Access here is for the project team and should stay with the people who are actively building.

Sandbox tenant

A copy used for testing configuration and integrations before anything reaches live business. It mirrors production closely.

Preview tenant

A tenant that shows the next Workday release, so teams can test upgrades before they arrive in production.

Production tenant

The live tenant that runs payroll, core HR and the rest of the business. Access here is the most sensitive and the most closely reviewed.

Integration tenant

A tenant used by integrations and automated processes. Access is usually given to service accounts rather than to people.

Training tenant

A safe space for training new users with realistic data, separate from anything that affects real workers.

How access is granted

Workday does not grant access to a person directly. Access is assembled from a few building blocks that work together, and it helps to know each one before you start.

  • Security groups decide who a rule applies to. A group can be based on a role, an organisation, a condition or a static list of workers.
  • Domain security policy decides what a group may do with a business object, such as view, edit or approve.
  • Role based access ties the two together, so a worker receives the domains that belong to their job.
  • Business process policy controls who can start, approve or view each step of a process.
  • Segregation of duties keeps conflicting permissions apart, so no single person can both request and approve a sensitive change.

Signing in and proving who you are

Interactive access should go through single sign on, backed by multi factor authentication. A central identity provider makes it easier to join, move and remove people, and it keeps a record of who signed in and when.

Service accounts and integrations are different. They should not use a person's login. Give each integration its own account, scope it to the smallest set of domains it needs, and rotate its credentials on a schedule.

A safe way to grant tenant access

  1. Start from the job. Describe what the person must do, then find the security groups and domains that match. Avoid copying another worker's access without checking why each group is there.
  2. Use groups, not individuals. Assign access through security groups so the reason for access stays visible and can be reviewed in one place.
  3. Keep production narrow. Give the widest access in build and test tenants, and the smallest access that still allows the work in production.
  4. Separate duties. Check for conflicts before you grant a powerful role, especially in payroll, security and integrations.
  5. Record the reason. Note why access was granted and when it should be reviewed, so the next person can follow the decision.
  6. Review on a rhythm. Run an access review each quarter, or after a reorganisation, and remove what is no longer needed.

Practices that keep access healthy

  • Give every person the least access that still lets them do the job.
  • Prefer role based groups over hand maintained lists.
  • Use single sign on and multi factor authentication for every interactive user.
  • Give each integration its own account with a narrow scope.
  • Rotate passwords and keys on a schedule, and after any suspected exposure.
  • Review who holds powerful security groups, not only who holds a job title.
  • Keep a clear audit trail and read it when something looks wrong.
  • Remove access on the day someone leaves, not at the end of the month.

Pitfalls to avoid

  • Granting access by copying a colleague, including permissions nobody needs.
  • Leaving a powerful group with a single member and no named owner.
  • Using a person's login for an integration, so the account outlives the person.
  • Giving production level access in a test tenant and then reusing the same habit in live business.
  • Letting access reviews become a rubber stamp that nobody actually reads.
  • Forgetting the preview tenant until an upgrade arrives.
Start from the job, grant through groups, keep production narrow and review on a rhythm. Clean tenant access is less about one big setting and more about a habit repeated every quarter.

Related reading: the salon guide to HCM essentials for HR professionals, the introduction to CyberArk security solutions for the security side of privileged access, the salon resource library, and the contact page for suggestions and corrections.