
Delegation in MSS: How Do Processes Keep Moving When the Manager Is Away?
Managers cannot always be at their computers. Daily meetings, presentations, visits they must attend, leave or sick days mean that they sometimes want to hand the requests coming from the system over to an assistant or a colleague in their team.
Delegation answers exactly this need: when the manager cannot be reached, leave requests, expense claims and other approvals do not wait, and work continues without interruption. But not every task should be handed to everyone. In this post we explain how manager delegation works in OrchestraHCM and the features worth knowing.
OrchestraHCM has two delegation methods:
- Full delegation
- Partial delegation
Full Delegation
With full delegation, the manager hands over all of their apps to a team member without selecting them one by one. When granting it, the manager enters the delegate, a start and an end date and, optionally, a note. The delegation is valid only between these dates and can be paused when needed.
The delegate signs in with their own user, sees the delegations given to them and switches to the manager's user. During this time they use the manager's inbox, team and apps as the manager would, and when they are done they switch back to their own user with one click. For the step by step guide, see Delegation.
There is one restriction, however: an app can be handed over to another user through delegation only if it is marked as delegable on the app side.
Which Apps Are Closed to Delegation?
For example, a manager cannot hand over apps that contain legal and pay related, sensitive information, such as their payroll, employment certificate or payslip. This has to be decided by HR from the very beginning. With the standard installation, OrchestraHCM does not allow personal apps containing payroll data and transactions to be delegated.
If you wish, you can make the same setting for other apps under System > Apps. When Delegable is cleared on the app's detail, the app:
- does not appear in the menu of a user working as a delegate and cannot be opened with a direct link either,
- does not send its workflow approvals to the delegate's inbox,
- is not among the apps that can be selected for partial delegation.
The rule is defined in one place and applies the same way to full and partial delegation, so managers do not need to think about which apps to exclude every time they delegate.
Partial Delegation
Partial delegation, as the name suggests, hands over only the approvals of the workflows the manager selects. For example, a manager can leave the approval of leave requests to their assistant and the approval of expense claims to another member of the team.
In this type of delegation, the delegate does not switch to the manager's user. They see the selected workflows in their own inbox and can approve or reject them directly with their own user. The delegate does not see the manager's other apps or data, which makes partial delegation the more controlled choice for everyday busy periods.
Which Delegation, When?
| Full Delegation | Partial Delegation | |
|---|---|---|
| What is handed over? | All apps that are open to delegation | Only the approvals of the selected workflows |
| How does the delegate work? | Switches to the manager's user and works in their place | With their own user, from their own inbox |
| When is it a good fit? | Long leave, sick leave, times when the manager cannot be reached at all | Busy meeting days, short trips, times when certain approvals must move faster |
| Sensitive apps | Apps closed to delegation cannot be opened | Apps closed to delegation cannot be selected |
System Administrators Switching to a User
Finally, a word on system administrators taking over a user, which we have not covered above. This case is a little different: the purpose here is to see the problems a user experiences in the system, or to test a newly added app with that user's authorizations. In other words, it is not a handover of work but a support and testing tool.
Good Practices
- Limit the delegation with dates. A delegation with an end date removes the risk of forgetting to close it after you return.
- Prefer partial delegation where possible. If only approvals must keep moving, there is no need to open all apps to the delegate.
- Use the note field. A short explanation such as "I will be on leave" lets anyone looking at the delegation list understand why it exists.
- Decide on sensitive apps during setup. If your company has sensitive apps besides payroll (for example compensation planning or disciplinary processes), close them to delegation before going live.
- Choose the delegate carefully. The delegate will approve on the manager's behalf; choose someone who knows the team's work and can carry that responsibility.
Ready to Explore OrchestraHCM?
To see delegation and manager self service in your own organization, get in touch with us.