Skip to main content
Everything you asked for and everything waiting on you, at /approvals. It sits in the workspace rather than the admin area, because who approves is a property of the request: this page is for the person who asked and the person being asked, neither of whom is necessarily an administrator. Part of the commercial edition. On a community deployment there is nothing here to answer.

​
What you see

Every request carries an expiry, so one nobody answered becomes Expired rather than sitting open forever.

​
What you can do

An approval is not a grant to the team, the month, or until somebody revokes it. A grant that outlives the reason it was given stops being a budget. The decision moves the row to its terminal state before anything is applied, so two approvers clicking at once produce one effect.

​
One level, and no chains

There is no counter-signing, no chain and no delegation. Those belong to whatever system your organisation already runs approvals in, and rebuilding them here would produce a worse copy. What the platform owes such a system is a record and a webhook. Escalation is also opt-in rather than automatic on every denial. Team quota usually clears within minutes as colleagues’ jobs finish, so routing every denial here would produce a queue of requests that answer themselves and an approver who stops reading the list.

​
Next

Working in a team · Teams · Billing