Workday names six HCM concepts you set up before staffing transactions and reporting: supervisory organizations, staffing models, job profiles, compensation, security, and business processes. Security and business processes are core across Workday, not only HCM. An agent that “designs the foundation” without these six in the tenant is writing fiction. Deployment Agent can inspect what you have already configured in a non-Production tenant. The concept topic describes that inspection as read-only. Workday’s Configuration Cloud announcement says Deployment Agent can also carry out approved changes, in opt-in early access for Workday partners since 18 November 2026.
What is structure, and what is your data
Workday provides metadata. You cannot change it. Tenanted data is your configuration and the data you add. The course’s picture is an apartment: plumbing and walls are metadata; furniture is tenanted data.
WDSetup is the internal tenant of factory default configuration implementers use when building a foundation tenant. It has configuration and setup data, and no worker or transactional data. The Configuration Catalog migrates packages from that content into your implementation and sandbox tenants, through Object Transporter, at no cost. You then change the content to match the customer. A package description includes the SKU, what is inside, and prerequisites. Test it before it moves toward Production.
Edit Tenant Setup - HCM is where the HCM course sends you for custom ID sequencing and system-wide defaults. Edit Tenant Setup - System is the example for banners and logos. Neither task is something Ask completes for you.
The six concepts, in the order they depend on each other
| Concept | What Workday says it is | What breaks if you skip it |
|---|---|---|
| ConceptSupervisory organizations | What Workday says it isThe management hierarchy. They hold the jobs and positions you hire into. Compensation, security, and business processes can all key off this structure. | What breaks if you skip itA hire has nowhere to land. Business process inheritance has no organization to select a definition for. |
| ConceptStaffing models | What Workday says it isChosen per supervisory organization. They decide how jobs are defined and filled, and how much control you keep. | What breaks if you skip itYou staff the organization in a way that does not match how you budget or fill jobs. The course does not say an agent should pick the model. |
| ConceptJob profiles | What Workday says it isThe job catalog. A generic description: skills, training, qualifications. Every worker has one. | What breaks if you skip itYou cannot describe the job you are hiring, and downstream objects that point at profiles have nothing to point at. |
| ConceptCompensation | What Workday says it isPackages group grades and plans. Grades carry ranges. Grade profiles localize them. Plans are the pay components, such as salary, hourly, and allowance. | What breaks if you skip itA hiring process that proposes compensation has no grade to propose. Workday’s own optimization prompt is about linking grades to job requisitions so high-volume hiring stays consistent. |
| ConceptSecurity | What Workday says it isFunctional areas, policies, and security groups. HCM areas named in the course include Staffing, Core Compensation, Organizations, and Personal Data. A domain collects tasks, reports, and data that share security. You cannot change the delivered domain or the items on it. You grant groups. | What breaks if you skip itThe right people cannot see the right tasks. The wrong people can. |
| ConceptBusiness processes | What Workday says it isDelivered types, customer-built definitions. What happens, which security group does it, and when. | What breaks if you skip itStaffing transactions do not route. The course says to configure the definitions before you staff the workforce. |
Business process definitions inherit. A subordinate organization uses the superior’s definition unless it has its own. The setup topic says Workday routes steps by organizations, roles, hierarchies, and locations.
How to use Ask without letting it invent the hierarchy
Work in an Implementation tenant. That tenant type is for prototyping, training, legacy loads, and testing. Confirm Ask with five calculation fields you can open in View Calculated Field. Then one chat per concept.
Supervisory organization and staffing
I am a Workday administrator. In my tenant, explain how supervisory organizations are structured for [top organization]. Which staffing model is on [organization name]? I will confirm in the organization view. Do not propose a new hierarchy.
Job profile and compensation
In my tenant, how is compensation grade [name] linked to job requisitions? List the grades you can see and the profiles that use them. I will open the grade.
That follows Workday’s published optimization use case and forces a tenant read. If the reply names grades you cannot open, stop. You are not on Ask, or the answer is incomplete. Workday tells you to expect incomplete answers.
Security
I am a Workday security administrator. In my tenant, which domain security policy controls [field], which security groups have View, and what would I change? I will edit the policy myself and activate pending changes.
Business process
In my tenant, which Hire business process definition applies to [supervisory organization] by inheritance? List steps and security groups.
Then open the definition. Effective date and errors change which definition runs. Ask does not activate security and does not edit the definition.
Delivered content versus your foundation
Use View Configuration Catalog Content for country-specific HCM setup you would otherwise rebuild. Customer Central’s setup topic gives a concrete case: a new office in France, and catalog content such as French time off plans, payslips, citizenship statuses, military statuses, and local termination reasons. Ask may suggest a package. The catalog is where you read the SKU and the prerequisites. Migrating it is Object Transporter, into an implementation or sandbox tenant, not into Production as an extract. Extracts do not load to Production.
Reference IDs on these foundation objects should be unique across tenants before the first migration. Object Transporter treats the same Reference ID and type as the same instance. Maintain Reference IDs is the bulk edit. A foundation built with different IDs in every tenant becomes a prerequisite pile.
Failure modes
| Mistake | What Workday’s pages imply |
|---|---|
| MistakeDesigning the supervisory hierarchy in a chat | What Workday’s pages implyInspection is read-only. The hierarchy is tenanted data. |
| MistakeTreating WDSetup or GMS as the customer tenant | What Workday’s pages implyWDSetup has no workers. GMS is fictitious demo data. |
| MistakeChanging “the domain” | What Workday’s pages implyYou cannot change delivered domains or the items secured to them. You change who is on the policy. |
| MistakeCopying a business process for every organization on day one | What Workday’s pages implyThe course recommends the default unless steps truly differ. |
| MistakeMigrating the foundation with workers in the same package | What Workday’s pages implyObject Transporter does not migrate transactional or reference data the way it migrates configuration dependencies. Check supported objects. |
| MistakeLetting Sandbox be the only copy of the foundation | What Workday’s pages implyA refresh replaces Sandbox with Production. Keep the foundation in an Implementation tenant or in an extract until it is migrated on purpose. |
Frequently asked questions
Can an agent propose the staffing model?
It can explain the concept in lay terms if you ask for knowledge discovery. The course says you choose the model per supervisory organization from your staffing and budgeting needs. Open the organization and set it. Do not take a model name you cannot find in the tenant as configured.
Do we load workers before the six concepts?
No. The course says the six are required before staffing transactions and HCM reporting. Workers also need job profiles. Pay groups and other payroll structures are a later configuration, not a substitute for the supervisory hierarchy.
Where should foundation configuration live?
Build it in an Implementation tenant. Migrate supported objects with Object Transporter after Reference IDs match. Use the catalog for delivered locale content. Use Sandbox to test against a Production copy, not as the only place the hierarchy exists.
How do we know Ask is describing our foundation?
It names objects you can open, after a prompt that says “in my tenant.” There is no on-screen indicator. A glossary answer with no names from your tenant is Q&A, which cannot see instances.
Sources checked
Public Workday course and admin-guide topics listed above, fetched 2026-11-16.