Practical guide
Workday Tenant Access: Getting In, Staying Safe and Working Well
Access to Workday is not a single door with a single key. Your organisation has its own tenant, and inside that tenant sit several environments, each with its own purpose, its own data and its own rules. Understanding that structure before you ask for access will save you time, help you ask for the right thing, and keep you and your organisation safer. This guide explains what a tenant is, how access is granted, and how to work well once you are inside.
What a Workday tenant is
A tenant is your organisation's own instance of Workday. It is kept separate from every other customer, and it holds your configuration, your data and your users. Within a tenant, Workday separates environments so that work can be built and tested before it touches live records.
Access is therefore both a security question and a practical one. What you can see depends on three things: which tenant you belong to, which environment you are working in, and which security groups your account has been given.
The environments you may need access to
Most organisations run a production environment alongside one or more test environments. The names may vary, but the pattern is common.
| Environment | Typical use | Caution |
|---|---|---|
| Production | Live people and finance data, used for real transactions | Tightly controlled; changes follow a formal process |
| Sandbox | Testing configuration and practising tasks | Data may be a periodic copy and can be stale |
| Implementation | Building and testing a new deployment during a project | Usually temporary and project scoped |
| Preview | Reviewing features that are about to arrive | Intended for assessment, not for live work |
How access is granted
Access is normally granted to a named person through a named user account, tied to a real individual rather than shared across a team. Your account is then placed into security groups, and those groups carry the roles and permissions that decide what you may see and do. Domain security policies describe the detail of those permissions.
Requests usually go through an owner or manager for approval, either as a ticket or as a formal access request. Two principles should guide what you ask for. The first is least privilege: request the smallest set of roles that lets you do the job, for the shortest time that makes sense. The second is segregation of duties: avoid combinations that create a control conflict, such as being able to both create a supplier and approve its payment.
Before you request access
- State the business reason and the specific tasks you need to perform.
- Name the environment you need, production or a test environment.
- Confirm who approves access for that area, such as a manager, a data owner or a system owner.
- Complete any required training or acceptable use acknowledgement first.
- Ask for a time limit if the need is temporary, so access can expire on its own.
Signing in safely
Where single sign on is offered, use it, and enable multi factor authentication if it is not already enforced. Keep your credentials unique to your work account, never share them, and never store them in documents, spreadsheets or chat messages. Follow your organisation's rules about approved devices and networks, lock your screen when you step away, and sign out fully on any shared machine.
Working well inside the tenant
Before you change anything, be sure which environment you are in. A banner, the page header or the web address will usually tell you, and the difference matters: a change made in production affects real people and real money. In a test environment, remember that data may be an old copy and that some connections to other systems may be switched off.
Test a change in a sandbox before it reaches production, and write down what you changed and why. A short note, kept with the request or the ticket, is worth a great deal when someone asks months later why a setting looks the way it does.
Access reviews and leaving
Good organisations review access from time to time, asking whether each person still needs each role. When someone changes job or leaves, their access should be removed promptly. If you suspect that an account has been compromised, report it at once through your organisation's security channel rather than trying to fix it quietly.
Common pitfalls
- Sharing one login across a team, which destroys the audit trail and hides who did what.
- Asking for broad administrator roles when a narrow role would do.
- Testing in production because it is the environment that is already open.
- Forgetting that a sandbox refresh can wipe test data or reset configuration.
- Keeping access long after a project has ended.
A quick access checklist
| Stage | What to confirm |
|---|---|
| Before requesting | Business reason, environment and tasks are clear |
| Requesting | Approver identified and least privilege applied |
| First sign in | Multi factor authentication on, password unique |
| Working | Environment checked before every change |
| Testing | Changes tried in a sandbox first |
| Reviewing | Access still needed and still appropriate |
| Leaving | Access removed and recorded |
Further reading
More from Anvil
Read the companion guide, Workday Training Requirements: Skills to Learn Before Starting, or browse the articles available online.