Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Inbox

The Inbox tab is your personal queue of decisions waiting on you. Each card is one document that has been submitted for approval and routed to you.

Reading a Card

Every inbox card shows:

  • Document label — a human-readable name for the document (e.g., the PO number, the SO number, the adjustment reference).
  • Total amount — when the document carries a monetary total, it is shown next to the label, formatted in the document’s own currency.
  • Document type — a small tag like PURCHASE_ORDER, SALES_ORDER, or INVENTORY_ADJUSTMENT, so multi-type inboxes are easy to scan.
  • Workflow name and level — which approval workflow this is, and what step in the chain you are at (e.g., Standard PO approval — Level 2).
  • Submitted date — when the originator sent it for approval.
  • Due date — the deadline for your decision, when the workflow has an SLA configured.
  • Overdue tag — appears in red when the due date has passed without a decision.

Reviewing the Underlying Document

Click View on the card to jump to the document under review (the PO detail, SO detail, or adjustment detail). This is the easiest way to inspect line items, totals, attachments, and history before deciding.

You can return to the inbox using the browser back button — your decision dialog state is not lost.

Approving

Click Approve to advance the request:

  1. A dialog opens with an optional Comments field — add context if you want it on the audit trail.
  2. Click Submit.
  3. The card disappears from your inbox. If there are more steps after yours, the next approver gets the request. If yours was the last step, the underlying document advances out of Pending Approval (e.g., a PO becomes Approved).

Rejecting

Click Reject to send the document back:

  1. A dialog opens with a Reason (required) field — explain why you are rejecting.
  2. Click Submit.
  3. The card disappears from your inbox. The originator is notified and can revise the document. The full decision history — including your rejection and reason — is kept permanently for the audit trail.

A rejection ends the entire request. The document can be edited and resubmitted, which starts a fresh chain.

Delegating

If you cannot make this decision (you are out, or someone else is better placed to judge), click Delegate:

  1. Pick a colleague from the Delegate to dropdown — only active members of your organization are listed, sorted by name.
  2. Add an optional comment.
  3. Submit.

The decision moves out of your inbox and into theirs, at the same step. You will not see it again unless they delegate it back.

For ongoing absences, ask an administrator to set up a delegation grant under Access Control > Delegations — that automatically forwards every decision assigned to you for the duration of the grant, without you needing to delegate each one by hand.

Deadlines and Escalation

When a workflow has an SLA configured (e.g., 72 hours per step), each card shows its Due time. If you do not decide by then:

  • The card is tagged Overdue and stays in your inbox.
  • Depending on the workflow configuration, the system may automatically escalate the decision — moving it from your inbox to the configured fallback approver (typically your manager in the hierarchy).

You will not be penalized for overdue items, but the originator’s document is held up until someone decides, so timely action keeps the business moving.

Notifications

You will receive a notification when a decision is first routed to you, and when a request you are involved in resolves. Check General > Pending Invitations for invitations and the email channel for approval pings.