Skip to main content
Wherever the product asks somebody to sign off before something proceeds, this is where that ask lands.

Reaching it

A stamp icon in the header, grouped with notifications and the sync tray — see the header for how that cluster works and why it moved there from the sidebar. Clicking it previews what is waiting on you; opening it fully brings up this screen.

The header stats

The first two are what you owe somebody else. The third is what somebody else owes you.

Two tabs

Everything with an open step where you are the approver. Each item names what it is, who asked, when, and what it actually is — a status change on a work order, a purchase request, a purchase order, or whatever else your organisation has put behind a chain.
Everything you have submitted that carries an approval, regardless of whose step it is on now. This is where you check on your own requests without having to go find each record.

Deciding an item

Two actions, and nothing else:
Reject always asks why. A rejection with no reason tells the requester nothing except that they must start over, and guessing what was wrong the second time is worse than asking once.
Approving does not necessarily finish the chain — a step you clear may hand off to another approver behind you. Rejecting does: one rejection stops the whole chain, and the record returns to whoever raised it with the reason attached.

What can carry an approval

Anything your organisation has put a chain in front of, configured on approval workflows: The same two actions apply everywhere. What differs is only what a chain was configured to guard, and who it names as approver at each step.

Why it moved out of the sidebar

Approving something is a thing you do in passing, on your way to whatever you actually opened the product to do — not a screen you plan a visit to. It used to be a sidebar item under Work; it now lives in the header instead, next to the other things worth a glance on every screen rather than a destination of their own.