Approvals Queue
Pending requests with context and age, approve or deny, expiry told to the asker.
Pending requests with context and age, approve or deny, expiry told to the asker.
Search blocks by description or jump to a page.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Approvals Queue is the pending inbox, three requests as cards where each one leads with who requests what: Priya Nair requests a production deploy, Jordan Lee a role change to Admin, and Omar Haddad approval for INV-2026-0341 at $480.00, which is over the $250 auto approve limit and says so in the context line. Approve and deny buttons sit at the card footer, indented to align with the body text. A 3 pending badge sits in the panel header and the footer states the expiry contract: requests expire after 72 hours and the requester is told so.
Requests are one array. The context line on each card is what stops the back and forth of why does this need approval, keeping it self contained for async review.
Reach for this block on the Approvals page or as a panel inside the notifications sidebar, wired to your approvals endpoint filtered to the current user and pending status. Approve and Deny should POST to your decision route with the request id and chosen action.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the workspace approvals inbox. Other approval queue shapes:
Tip: the auto expiry line in the footer is not fine print, it is the reason requesters feel safe submitting without chasing the approver manually.