A Workday tenant is the isolated environment in which an organisation runs Workday. Access to that tenant is granted through user accounts, security groups, roles and authentication controls, and it is maintained through the joiner, mover and leaver lifecycle.
This article explains what a tenant is, how access is usually granted, and the controls that keep access accurate as people join, change role and leave.
Workday describes each customer organisation as a tenant. The tenant has its own address, its own configuration and its own data, and it is separated from every other customer on the shared service. Large organisations sometimes run more than one tenant, for example a production tenant and one or more non production tenants used for testing and training.
Non production tenants matter because they mirror the production configuration closely enough to test changes safely. Access to them should be managed as carefully as access to production, because they often contain copies of real worker data.
Access is not usually granted person by person. Workday uses security groups, and a user receives access by being placed in the groups that match their role. Two broad kinds of group do most of the work.
Role based groups assign access according to a person's position, supervisory organisation or job. They follow the worker as the worker moves, which reduces the chance that access is left behind after a transfer.
User based groups are maintained by hand and are useful for small, stable populations such as a project team or an integration support group. They require a clear owner, because nothing changes them automatically when the person's job changes.
Workday also applies domain security policies, which decide what a group can see and do in a particular area of the system. A well designed tenant combines groups and domain policies so that the default is no access, and every additional permission has a reason.
Most organisations connect the tenant to a central identity provider so that people sign in with their corporate credentials. Single sign on reduces the number of passwords in use, and it lets the organisation enforce multi factor authentication at the identity provider rather than inside Workday.
Where single sign on is not used, the tenant should still enforce a strong password policy and multi factor authentication for privileged accounts. Integration users, which are accounts used by other systems rather than by people, need particular attention. They should be limited to the specific operations they perform, and their credentials should be rotated and stored securely.
Access should follow the worker lifecycle rather than being handled as a series of one off requests.
Automating these steps, where the tenant and the identity provider support it, reduces both delay and error. The aim is that the joiner, mover and leaver outcome is the same whether or not someone remembers to raise a ticket.
Give each person the access needed for the current role and no more. Sensitive areas such as payroll, compensation, security configuration and integration setup should be limited to a small group, and the membership of those groups should be reviewed more often than the rest.
Some combinations of access create a conflict, for example the ability to both create a payment and approve it. Identify those combinations in advance, and use the tenant's controls or a manual review to stop one person holding both.
The tenant records a great deal of activity. Useful signals include login history, changes to security group membership, changes to domain security policies, and the actions of integration users.
Review these on a regular schedule and alert on unusual patterns, such as a spike in failed logins, a privileged group gaining members outside a change window, or an integration user calling operations it has never used before.
An access review asks the owner of each group to confirm that every member still needs the access. Reviews work best when they are small, frequent and tied to a named owner. A single annual review of every group is easy to postpone and easy to approve without thought.
Record the outcome of each review, including any access that was removed and the reason. That record is useful both for audit and for improving the review itself.
Write down who owns each security group, what the group is for, and how membership is decided. Keep the tenant configuration under change control, and treat a change to access as a change that needs testing in a non production tenant first. Agree a small set of measures, such as the time to remove access after a leaver, the number of orphaned accounts, and the proportion of groups reviewed on schedule.
Begin with the groups that touch payroll, security configuration and integration. Confirm that each has an owner and a current membership list, remove access that cannot be justified, and schedule the next review. Then repeat for the next most sensitive area. Access improves fastest when each step is small, visible and measured.
Tenant access is not a one time setup task. It is a continuing process that keeps the right people working in Workday and everyone else out.