Management Model

Dayforce Implementation Guide

Version
R2025.1.1
Management Model

Dayforce’s management model can support a mix of the following management modes:

  • Derived by org: Users who manage a location are the manager of the employees with a primary work assignment at that location by default.
  • Direct manager: Users can be assigned to manage specific employees no matter where they physically work.

Note: A third option, job assignment management, is also available. See Management by Job Assignment Overview.

This management model gives flexibility to organizations to manage employees differently depending on their job assignments.

For example, in a retail organization, the accounting, marketing, and other corporate-level departments are managed using the direct manager mode, where the VP of marketing manages the marketing employees, even though they all work in physically separate offices. At the store level, employees like cashiers, receivers, and sales associates are managed through the derived by org method by the manager of the store.

Order of Precedence

When both management modes are used, direct management takes precedence over derived by org management.

For example, Amanda’s primary work assignment is at the Bayview location. By default, Amanda is managed by the Bayview location’s manager, Stephanie, through the derived by org mode. If you need a different user to manage Amanda, you would assign Amanda a direct manager. When you do this, the direct manager replaces Stephanie as Amanda’s manager.

Conversely, if you delete the direct manager and don’t add a new one, Amanda goes back to being managed by Stephanie by default.

Changes to Primary Work Assignment

The Dayforce management model links the manager to the employee based on the employee’s primary work assignment, which is defined in the Work > Work Assignment screen of People (an employee can only have one active work assignment at a given time).

Updates to the primary work assignment record can result in automatic updates to the employee’s manager in the following cases:

  • An employee is managed by org, and you create a primary work assignment record or update the existing record to a different location. As a result, the employee’s previous management by org relationship is end-dated, and they default to being managed by org by the manager of the new location.
  • An employee has a direct manager, and you create a primary work assignment record (so that the old record is end-dated). As a result, the employee’s direct manager relationship is end-dated, and they default to being managed by org by the manager of location in the work assignment record. In this case, you can assign the employee a new direct manager to replace the managed by org manager.
  • An employee is managed directly, and you update their existing primary work assignment record to a different location. Because the existing work assignment record wasn't end-dated, the employee’s direct manager remains the same.

Automatic Effective End Date

If you assign a direct manager to an employee (for example, in the Managers section of the Work > Management Assignments screen of People), and the associated primary work assignment has an effective end date defined, Dayforce automatically assigns the management record the same effective end date as the corresponding work assignment. A warning message is also shown indicating that the effective end date was assigned.

For example, an employee has an active work assignment from July 1, 2020 to August 31, 2020, and you create a direct management record with an effective start date of July 15, 2020 and leave the effective end date undefined. When you save, Dayforce automatically assigns an end date of August 31, 2020 to the direct management record.

Employee Access

The application uses the list of employees that a user manages to determine which employees they can access in Dayforce.

Employee access is described as follows for the management modes:

  • Derived by org: Users who manage a location can access all of the employees who have a work assignment there, including employees at the location who have a direct manager. Continuing the earlier example, store manager Stephanie has access to Amanda, even though Brian is Amanda’s direct manager.
  • Users who manage a location can also access employees at locations under the assigned location in the org hierarchy. For example, a manager of a district location has access to the employees of the stores in that district.
  • Note: It’s also possible for users to be assigned access to a location without being a location manager. This type of access is typically enabled for administrators and is configured in the Location Access tab of their user account in System Admin > User. Users with location access have access to employees at the assigned location and locations below it in the org hierarchy.
  • Direct manager: Users who are assigned employees through the direct management mode, and who aren’t location managers or administrators assigned location access, can access employees who report directly, or indirectly, to them.
  • For example, if Maury reports to Erin, who reports to Fran, who reports to Julie, then:
    • Julie has access to view Fran, Erin, and Maury.
    • Fran has access to view Erin and Maury.
    • Erin has access to view Maury.
  • As another example, a manager can see the schedule and timesheet of the employees who they directly and indirectly manage, provided they have the necessary role features and access authorizations to use those features.
  • Dayforce automatically assigns the appropriate entries in the org picker for users who manage employees directly and indirectly. For example, the manager can select the location where their employees work in the org picker.

Role Features and Access Authorizations

While the management model provides access to employees, it’s the user’s role features and access authorizations that determine which features they can access those employees in, and which information they can view and update for those employees.

Continuing the earlier example, say that Amanda’s direct manager Brian needs to approve her time away requests, and Stephanie, the manager of the Bayview store, needs to create schedules and review timesheets for the employees at her location.

These requirements can be accomplished with the following configuration:

  • As store manager, Stephanie has access to employees who have a work assignment at the Bayview store, including Amanda. Stephanie is also assigned the role features and access authorizations for viewing and editing schedules and timesheets. 
  • Brian is Amanda’s direct manager and is assigned the role features and access authorizations for reviewing and approving time away requests. He doesn’t have role features and access authorizations for loading or editing schedules and timesheets.

If it’s later determined that Brian should have access to Amanda’s schedules and worked shifts, users can assign him an appropriate role.