Read and decide on a request
One page holds everything about a request: what was asked for, where it stands, who has already decided — and, when it is your turn, the buttons to decide yourself.
Find a request
“Requests” in the top navigation lists every request you are allowed to see, with filters for workflow, status, date and free text. Approvers can also jump straight there from the email or the Slack message that told them it was their turn.
A request is visible to the person who sent it, to every approver in its chain, to administrators, and to anyone granted “Can view requests” on that workflow. Nobody else in the organization can open it.
Read the request
The header carries the workflow name, who requested it and when, and the status — New, In progress, Completed or Declined. Below that:
- Submitted details — every field of the form as it was filled in, attachments included.
- Approval flow — the stages in order, each marked Approved, Declined, Awaiting, Upcoming or Canceled, with every approver and their own decision.
- Activity — a timeline of who did what, when, and what they wrote about it.
Approve or decline
The “Your decision” panel appears only for the people the request is currently waiting on — if it is not your turn, or the stage has already been decided, there is nothing to press.
The comment box is optional when you approve and required when you decline, so a rejection always comes with a reason the requester can act on.
The buttons are named by the workflow — “Approve” and “Reject” unless the stage renamed them. There is no separate “request changes” action: send it back with a comment explaining what to fix, and the requester submits a corrected request.
Who hears about it
Approvers are notified when a request reaches them, and the requester is notified when it is finally approved or declined. Each person chooses their own channels — email, Slack or both — in Settings.