In Workday HCM, role-based (constrained) security groups control access to business processes and data based on an individual’s organizational assignments. The Access Rights to Organizations setting determines which organizations—and therefore which workers—fall within the scope of responsibility for users assigned to that security role.
When the Access Rights to Organizations setting is configured as Current Organization and All Subordinates, the HR Partner assigned to a supervisory organization gains security access to that organization and every subordinate organization beneath it in the hierarchy. This access applies regardless of whether subordinate organizations have their own HR Partners assigned.
In the context of employee terminations, this means HR Partners are responsible for approving termination events for employees who belong to the organization they directly support as well as employees in any subordinate supervisory organizations. Workday evaluates the worker’s organizational membership at the time of the transaction and routes the business process approval accordingly.
Options B and C are incorrect because Workday does not limit approvals based on whether subordinate organizations have HR Partners or restrict access to a single subordinate. Option D is also incorrect because it ignores subordinate organizations entirely, which contradicts the selected access rights configuration.
From a Workday Pro HCM security design perspective, this setting ensures appropriate oversight and continuity by allowing HR Partners to support broader organizational segments without creating security gaps. It is commonly used in shared-services or regional HR models where HR Partners support entire organizational branches.
Therefore, the correct and Workday-verified answer is that HR Partners must approve termination events for employees in their assigned organization and all subordinate organizations.
