All documentation

Administration

Settings

Every configuration surface, and what each one refuses in order to protect what already happened.

The structural pieces underneath — legal entities, working patterns, holiday calendars, cost centres and positions — have their own page: Entities, patterns and cost centres. What each editor refuses on a people record is collected in When HR refuses.

Every settings screen answers the same question before it saves: what already happened under the old rules? The answer is different for each one, which is why the delete behaviour differs.

SettingWhat deleting does
Leave policyRefused where the ledger points at it — that link is how somebody answers what rules a balance was credited under
Overtime ruleEnded rather than removed where it has classified approved time, or an old timesheet becomes unexplainable
Checklist templateDeactivated where a checklist has started, so which version somebody went through survives
Agreement templateDeactivated where it has produced a document, for the same reason
Approval policyDeleted outright — the decision itself records how it was reached
DelegationEnded today where it has started; removed outright where it has not
Working patternRefused while any engagement uses it — those people would silently lose all scheduled hours
Holiday calendarRefused where it holds past dates, because absences were costed around them
Credential classRefused while somebody holds it — it would stop being recognised without leaving their record

Configurations that are refused outright

Three would save cleanly and then behave wrongly, which is the failure these forms exist to prevent:

  • A leave entitlement below the statutory minimum recorded on the same policy.
  • An overtime rule with no thresholds at all — no rule is reported honestly as *no premium calculated*, but an empty one looks configured and silently pays everything at single time.
  • An approval chain with neither self-approval nor an HR fallback, which blocks a managing director's own request permanently.

Changing an entity's standard working day

Entitlements are stored in minutes and rendered as days against it. Changing it restates every balance expressed in days across that entity without moving a single stored minute. The form warns, and the audit entry records both values, because somebody will eventually ask why a balance reads differently.