Collaboration

Approvals

Four-eyes control for high-risk actions: what needs approval, the queue, deciding, delegation, and the decision trail.

What needs approval

The approvals system routes high-risk actions through a second pair of eyes before they execute. The supported kinds:

• Large adjustments — stock corrections beyond your policy's size.
• Archive with stock — retiring a location or item that still holds quantity.
• Item merges — consolidating duplicates.
• Bulk deletion — mass destructive changes.
• PO over budget — purchase orders exceeding the budget policy.

(Approvals are a plan capability; which actions require them follows your organization's policy.)

The queue

Approvals (Admin group) lists requests — yours pending, all pending, recently decided — each with its kind, summary, subject links, requester, and deadline.

Deciding

Open a request to approve, reject (a reason is required), or delegate it to someone better placed; requesters can cancel their own. Two hard rules keep the control honest: a requester can never decide their own request, and every decision lands in the audit log with its reason. Decisions notify the requester via the approval-decision notification kind.

Deadlines keep requests from rotting in the queue — an undecided request blocks its action, which is the point.