Approval delegations

Register temporary delegations: during the period, approvals that would go to the absent person go to the delegate instead. Without delegation, pending items from someone who is away will breach the SLA.

Outside the period the delegation doesn't apply — approval goes back to the holder without anyone needing to turn anything off. Leaving the end blank creates a delegation with no deadline, which is the kind that usually gets forgotten switched on.

The Save button starts dimmed on purpose and lights up the moment you change any field — that's what prevents accidentally saving a record identical to the one that was already there. If it stays dimmed after you fill things in, the change wasn't recognized: change a field's value and the button lights up.

Delegation exists to cover your absence, so the recipient has to be someone else. The screen refuses and explains when the delegate is the delegator themselves.

You don't need to undo anything when you come back. On the end date the approval authority returns to the holder at that very instant, and the delegation starts appearing in the list as closed — kept there on purpose, to answer later "who could approve in June?". A delegation without an end date is the recipe for "nobody knows anymore who approves what": always prefer a closed period, even a long one.

Delegation transfers the power to APPROVE, and nothing else. It doesn't give the recipient the screens, reports or data the holder sees — that still comes from each person's profile. If the person needs to see something they don't see today, the path is the access profile, not the delegation.

Both. Every approval made via delegation records the name of who approved AND of who delegated, with the date. That's what allows reconstructing the decision months later without depending on anyone's memory — and it's the reason delegation is preferable to the shortcut of lending your password, which erases that information.