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.
Workday
How tenants are organised, how access is granted by role, and how to keep it clean and auditable.
Workday
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.

The essentials
Most Workday landscapes follow the same pattern. Knowing the purpose of each tenant makes access decisions much simpler.
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.
A copy used for testing configuration and integrations before anything reaches live business. It mirrors production closely.
A tenant that shows the next Workday release, so teams can test upgrades before they arrive in production.
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.
A tenant used by integrations and automated processes. Access is usually given to service accounts rather than to people.
A safe space for training new users with realistic data, separate from anything that affects real workers.
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.
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.
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.