Approval policy

The one place that says what needs approval, when, and who decides. Every form, inbox item and permission text in the back office reads this matrix; nothing is typed a second time on another screen.

Tasks & approvals Roles & permissions

Approval matrix

WhatModuleGoes to approval whenFirst approverSecond approverIf nobody decidesSourceConfigured limit
Rows are read from the shared policy record at run time. Links such as set-approvals.html#refund from other screens land on the matching row. A limit typed here is used by the simulator on this page only: the prototype does not save it.

Open items under DEC-03: questions this matrix does not answer yet

QuestionWhere it comes fromWhat the prototype does meanwhileRow affected
These are not decided on this page. They are listed so that management review covers them together with the limits.

Try a request

Approval route from the matrix

    The route is computed on this page from the matrix row, the amount and the requester. It is a demonstration of the rule, not an authorisation service.

    Who holds each approver function

    Responsibility profiles
    Approver function in the matrixRoleHeld byRows
    People and roles come from the employee and role records. A person can hold several roles. Changing who holds a role is done in Roles & permissions, not here.

    Delegation and separation rules

    FromToCoversUntilStatus
    • Nobody approves their own request. If the requester holds the approver function, the item goes to another holder of that function or to the next approver.
    • A delegated decision is recorded with both names in the audit log.
    • A delegate cannot delegate again, and delegation never lowers a limit.
    • Who may delegate what, and for how long, is not decided yet. The line above is a sample, not an approved rule.

    Who can change this policy

    RoleViewPropose a changeApprove a changeExport

    Shown as a proposal for management review. Hiding by role is static in the prototype and is not proof of production authorisation.

    Where this policy is used

    ScreenModuleRows it rendersHow it shows them
    Each screen calls the same helper with the row key, so the text, the approver and the link back to this page cannot differ between screens.

    Conflicts found and removed

    ScreenOld text on that screenWhat the matrix says now
    The old texts are kept here as evidence of the defect (FIN-05). On the screens themselves they are replaced by the matrix row. Which value is right is a management decision: see the open decision below.

    Version history

    • v0.2: the six conflicting texts were collected from the screens and listed
    • v0.1: the matrix that was already configured in Organisation, approval thresholds

    No version of this matrix has been approved by management.