1.4 Organizations in Workday

Why an administrator has to know the organization model

The Workday Platform module asks you to identify organizations in Workday. The reason this appears in a platform exam rather than only an HCM exam is that organizations are the anchor for two things you will configure constantly:

1. Business process routing - approval steps route to roles such as Manager or HR Partner, and those roles are assigned on organizations.
2. Role-based security scope - a constrained role-based security group grants access to target data in the organizations where the member holds the role.

Change the organization structure and you change who approves what and who can see whom. That is why organization questions on this exam usually have a security or routing twist.

Supervisory organizations

Supervisory organizations group workers into a management hierarchy. Workday's courseware calls them the foundation of Workday HCM: they contain the jobs and positions that workers are hired into, and compensation, security, and business process workflows can all be configured against them.

Key structural rules:

• Every worker belongs to a supervisory organization.
• Supervisory organizations link into a superior/subordinate hierarchy. The organization above is the superior; those below are subordinates.
• A subordinate organization has exactly one immediate superior at any single point in effective time.
• The organization at the root has no superior.
• Each supervisory organization is associated with a staffing model, which determines how jobs are defined and filled. (Staffing model configuration itself belongs to the HCM Core track, not this exam - but recognizing that the association exists is fair game.)

                 ┌─────────────────────────┐
                 │  Global Modern Services │   (top-level, no superior)
                 └────────────┬────────────┘
              ┌───────────────┴───────────────┐
              ▼                               ▼
      ┌───────────────┐               ┌───────────────┐
      │  Field Sales  │               │   Technology  │   (superior orgs)
      └───────┬───────┘               └───────┬───────┘
        ┌─────┴─────┐                   ┌─────┴─────┐
        ▼           ▼                   ▼           ▼
   ┌─────────┐ ┌─────────┐        ┌──────────┐ ┌──────────┐
   │ US East │ │ US West │        │ Platform │ │ Security │   (subordinates)
   └─────────┘ └─────────┘        └──────────┘ └──────────┘

Functional and financial organization types

A business is not only a reporting line. Workday delivers additional organization types that model other dimensions of the same workers, without disturbing the management hierarchy.

Most of these types support hierarchies of their own - a cost center hierarchy, a company hierarchy, a region hierarchy - used for roll-up reporting and for assigning a role once at a high level rather than on every node.

Distinguishing question the exam likes: which organization type represents a legal entity with its own ledger and tax identity? Company. Which one tracks spend without changing who a worker reports to? Cost center. Which one adds a dotted-line manager without changing the primary reporting line? Matrix organization.

Organization assignments and inheritance

Supervisory organizations are connected to functional and financial organizations through organization assignments. Two flavors matter:

• Default organization assignments pre-populate the company, cost center, region, and similar values on staffing transactions for positions in that organization. They reduce data-entry error.
• Allowed organization assignments restrict which values a user may pick. If a supervisory organization allows only a defined set of cost centers, a user cannot assign one outside that set.

Inheritance: a subordinate supervisory organization inherits its superior's default organization assignments unless an explicit override is saved on the subordinate. This is why a reorganization can silently change costing for a whole branch - the branch was inheriting, and the new parent has different defaults.

Organizations, routing, and security together

Bring the pieces together with a single worked scenario.

A change job event is initiated for a worker in US East. The business process definition includes an approval step routed to the Manager role and a second approval routed to the Cost Center Manager role.

• Workday resolves Manager from the worker's supervisory organization - the manager of US East.
• Workday resolves Cost Center Manager from the worker's cost center organization assignment - a different person entirely, reached through a different organization type.
• If the role is unassigned on that organization, the step has no assignee and the event stalls. Workday looks up the hierarchy for an inherited assignment, which is why roles are commonly assigned high in a hierarchy and left to cascade.

A constrained role-based security group behaves the same way: an HR Partner assigned on US East sees target data for US East and its subordinates, not the whole tenant.

That is the single most important organization takeaway for a platform administrator. Organizations are not decoration; they are the coordinate system that routing and constrained security both read.