Skip to main content
Italian Oral History Institute Los Angeles, California
Institute seal
I.O.H.I. Italian Oral History Institute

An archive of Italian life in California, built from people's own words.

Reference

Workday Tenant Access

How a Workday tenant is structured, how access is granted, and how to keep that access under control.

Introduction

Access is a set of decisions, not a switch

A Workday tenant is a separate copy of the platform that belongs to one organisation. It holds that organisation's data, configuration and security rules, apart from every other customer on the shared service. Access to a tenant is therefore not a single switch. It is a series of decisions about who may enter, what they may see and what they may change.

Getting those decisions right matters more than the size of the organisation. A small team with a clear model is safer than a large one that grants broad access because it is quicker than thinking.

One platform, several tenants

Most organisations run more than one tenant. A common set includes an implementation tenant for building and testing, a sandbox for practice and training, a preview tenant where upcoming releases can be seen before they arrive, and the production tenant where real work happens. Each tenant has its own access rules, and the same person may hold different rights in each.

That separation is a safeguard, not a formality. Testing a security change in a sandbox first is the cheapest way to avoid breaking production on a Friday afternoon.

How access is granted

Access begins with a user account, but an account on its own grants very little. Workday controls access through security groups. A person is placed in one or more groups, and each group carries permissions over particular domains of data and particular business processes.

Two layers matter most. Domain security policies decide which data a group can see and act on. Business process policies decide which steps a person may take within a process, such as approving a request or correcting a record. A sound model uses both, so that seeing data and acting on it remain separate decisions.

Groups can be built around roles, jobs, organisations or a fixed list of people. Role and job groups scale better than hand maintained lists, because they follow the organisation as it changes.

Authentication

A password alone is a weak front door. Most organisations connect Workday to a central identity provider through single sign on, so that the same credentials and the same rules apply across systems. Multifactor authentication adds a second check, and should be required for anyone with elevated access.

Single sign on also makes deprovisioning safer. When a person leaves, disabling the central account closes the Workday door at the same moment.

Integration and API access

Not everyone who reaches a tenant is a person. Integrations use their own accounts, often called integration system users, and reach the system through an API rather than a browser. These accounts deserve the same care as human ones, and often more, because they can move large amounts of data without anyone watching.

Scope each integration to the smallest set of operations it needs. Rotate its credentials on a schedule. Keep an owner's name against every integration account, so that when something changes there is someone to ask.

The access lifecycle

Access has a life. A new starter needs an account and the right groups on the first day. A person who changes team needs old rights removed as well as new ones added. A leaver needs everything closed promptly.

Three habits keep this under control. First, a clear request path for new access, so that grants are recorded and justified. Second, a periodic review in which managers confirm who still needs what. Third, a firm rule that access is removed when it is no longer needed. Reviews can sound like paperwork until the first audit, when they become the evidence that the model works.

Auditing and least privilege

Least privilege is the principle that a person should hold only the access required for their work, and only for as long as they need it. In practice it means resisting the easy grant of a broad group, and choosing narrower groups that can be justified.

Workday keeps records of who changed what. Those records are only useful if someone reads them. A short, regular review of security changes, failed sign in attempts and new integration accounts will surface most problems before they grow.

Watch for these

Common pitfalls in tenant access


Most access problems are not attacks. They are small conveniences that were never undone.

A single wide group solves today's problem and creates next year's. Prefer narrow groups that match the task, and keep a written reason for every exception. If an exception is needed, give it an end date.

People move, projects end and roles change, but grants tend to linger. Run a review at a fixed interval, and treat silence as a reason to remove access rather than a reason to keep it.

An integration account that nobody owns becomes invisible. Name an owner, record what it does and which data it touches, and remove it when the integration is retired.

A policy that looks harmless can lock out a team or open a gap. Change access in a sandbox first, confirm the effect with the people who do the work, then apply it to production.

A review postponed once tends to be postponed again. Put it on the calendar, keep it short, and record the outcome. A modest review that takes place beats a thorough one that does not.

Access as a continuing practice

Tenant access is not configured once and forgotten. People join and leave, roles shift, integrations come and go, and the platform itself changes with each release. Teams that treat access as a continuing practice, with clear groups, steady reviews and an owner for every account, find that the awkward questions become routine rather than urgent.

A short checklist

  • Know which tenants exist and who owns each one.
  • Grant the smallest group that does the job.
  • Require multifactor authentication for elevated access.
  • Give every integration account an owner.
  • Review access on a fixed schedule and record the result.