- New Organization Designer user interface -
This section describes how to manage positions using the new user interface for the position panel. If your organization uses the original version, see Manage Positions (Original Organization Designer User Interface). To understand which version you’re using, see Organization Designer User Interface.
If your organization uses Position Management, you can view the position hierarchy in People in the Positions screen, or by going to Organization Designer and clicking the positions icon on the left side of the screen. When you select a position, the position panel opens on the right side of the screen. The position panel has three tabs: Information, Occupants, and Audit. Each tab has one or more subtabs with different kinds of information.
An employee can occupy more than one position. For example, Ramesh is a direct report of Maria but also occupies the Finance Associate position where they report to Alex.
Locations for positions are configured in Org Setup > Jobs and Job Assignments.
If a position manages other positions, its position card shows the number of direct reports and the number of total reports for the position:
As the position card illustrates, Shaine is a regional manager with 2 direct reports and 12 total reports. The total reports include Shaine's direct reports and all of the positions under them.
Note: You can delegate access to Organization Designer > Positions to another user so that they can complete tasks in the feature.
Edit Access to Positions and Position Occupants
In Organization Designer, managers have access to the same employee information as in other areas of Dayforce. In the Position Management model, positions are separate from the employees who occupy them. As a result, although managers can update positions that report to them indirectly, they can’t update details about the employees that occupy those indirect report positions such as their expected vacancy date.
For example, a store manager has several department managers as direct reports, who in turn have sales associates reporting to them. The store manager can update position details for any of the department managers and sales associates that are under them in the position hierarchy. However, they can update occupant details only for the department managers because they don’t have access to the employees who occupy the sales associate positions. This example is shown in the table below.
| Role | Direct and Indirect Reports | Permission to Modify Employee Details | Permission to Modify Position Information |
|---|---|---|---|
| Store Manager | Direct: Community Manager | Yes (can access direct report employee information) | Yes |
| Store Manager | Indirect: Sales Associate | No (no access to indirect report employee information) | Yes |
| Department Manager | Direct: Sales Associate | Yes (can access direct report employee information) | Yes |
Workflows and Edit Modes for Positions
Managing positions works differently depending on whether your organization uses workflows and edit modes for position updates.
If your organization uses workflows without edit modes, any user with access to the Positions screen in Organization Designer can update all attributes for the positions they have access to. All changes go through the same workflow approval process before they’re applied.
Edit modes provide an additional layer of control by restricting which position attributes users can update at the user-role level. A different workflow can be linked to each edit mode so that different types of updates go through different workflow approval processes.
When edit modes are configured, the position hierarchy loads in a read-only state. To begin making changes, users must select an edit mode from the drop-down list:
After the user saves their changes, the updates are sent for approval based on the workflow configured for the edit mode.
If workflows haven’t been configured correctly, the position hierarchy is read-only, and an error message tells you to contact your Dayforce administrator. This issue usually means that the workflow form hasn’t been configured correctly in Workflow Administration > Role Privileges.