

Reaching it
Approvals is not in the sidebar. Open it from the stamp icon in the header, which carries a count of the steps waiting on you; clicking it previews them (each with its request, step and who asked) and Approvals opens this screen. Your profile also links here from Waiting on you. Everybody can open the screen — what you see on it is only what involves you. Approvals can also be decided from the buttons in an approval email — see approving from an email. A link can open one request directly. The email that tells you a request was sent back to you for revision opens it on You asked for, and a link to a request you hold a step of opens that step on Waiting on you. Closing the dialog leaves you on the list.The stat strip
Where a request stands
Every approval screen — the tabs here, the dialogs, a record’s own approval card and Workflow activity — describes a request in the same words:Three tabs
Waiting on you
Every open step you can clear, the longest wait first. Site, location, company and business unit are on the row by default, the same four columns on every tab, so you can see whose money it is and where without opening it.
Overdue rows are tinted red. When nothing is waiting the tab reads Nothing is waiting on you.
Asked of you
Requests an approver has asked you to look at before they sign. You are not approving these — you are acknowledging that you have checked something. Columns: Request, Asked by (the approver who asked you), Raised by, Site, Location, Company, Business unit, What they asked and Waiting, with Step available from Columns. When it is empty the tab reads Nobody is waiting on your view.You asked for
Every request you raised that carries an approval, whoever’s step it is on now. It also lists requests a colleague sent about a record you wrote: you are that request’s author, and it comes back to you, not to them, if an approver sends it back for revision.
A request sent back to you for revision is tinted blue, one waiting on a step nobody can clear is tinted amber, and one approved but not carried out is tinted red.
Each tab has Filter and Columns like every other list, and Select all for bulk actions.
Deciding a step
Click a row on Waiting on you to open it.

- Asked by, Kind and Raised, then Site, Company, Business unit, Location and Category — where the work is and which part of the business it belongs to. Location and category are given as whole paths, such as Tower A › Floor 3. All of these are always shown, with a dash where the record has none, so every request reads the same way.
- Level — for example Level 1 of 3, with Next: and who signs after you, or Last level.
- Why you — which of your authorities makes you an approver on this step, or “Forwarded to you by” the approver who handed you their place. A forwarded request also says who forwarded it to you and when, with their reason, and that it is yours to decide in their place and cannot be forwarded again.
- What is being asked for, where the request is an action rather than a form — the new deadline on a request for more time, for example. A request for more time shows only the deadline, not the job’s planned start and end, which it does not change.
- What would change, where the request changes fields on a record — each Field, what it is Before and what it would be After. Values from the product’s fixed lists are shown in words.
- The record itself — every field of the requisition, asset category or whatever it is about, with its attached files — so you decide on what is actually there.
- Lines, where the request has them (a requisition’s lines, for example) — see deciding line by line.
- Where it has got to — every level of the chain in order, each labelled Level 1, Level 2 and so on, with who may sign it and where each step stands (see the chain). A signed step shows the approver’s job title beside their name. Levels the request has not reached yet are drawn dashed and marked Upcoming, naming who will be asked.
- Where it came back to you, why: Rolled back to you by the approver who rolled it back, with their note; or, after a revision, who sent it for revision and when, what they asked for, and when it was sent again with the initiator’s note.
- Remarks, unless your workflow hides them — an empty box, “Optional. Sent with your decision.” Where the workflow requires a remark it says “Sent with your decision. This workflow asks every approver for one.”, and Approve waits until you have written one.
- Attachment, where your workflow asks for a file with each decision — Attach a file adds one, “Kept with your decision on this approval, not on the record.” Where the file is required, the dialog says “This workflow asks for a file with every decision. Attach one to approve or reject.”
The five answers
An approver has up to five answers, in the order of how much each costs the person who asked:
Switching between answers swaps the default wording to match, but never overwrites a remark you typed yourself. Cancel closes a panel without sending anything.
If somebody has been asked to look at the request and has not answered, every answer is held, Forward included: “Waiting on an acknowledgement, so this cannot be approved, sent back for revision, rolled back or rejected yet.” Take the ask back if you no longer need it.
If somebody else decided the request, or sent it for revision, while you had it open, your answer is refused with the reason, the buttons are withdrawn, and the list refreshes when you close the dialog.
Signing on behalf of somebody
If somebody has delegated their approvals to you, Signing as offers Myself or On behalf of that person. The decision is recorded as yours, with the authority you used named beside it. Forward hands on only your own place, so it is unavailable while you sign for somebody else: “Forward hands on your own place on this step, so it is not offered while you sign for somebody else.”Asking somebody to look first
Want somebody to look at this before you sign it? — Ask somebody lets you pull a colleague in before you decide.
Click Ask them. The request then appears on their Asked of you tab, and your step is held until they answer. Take it back withdraws the ask.
Deciding line by line
On a request with lines, each line shows what was Asked for, what is Allowed and a Verdict. Anything you leave alone is approved as it was asked for — you do not have to touch a line to agree with it. For a line you disagree with:
Record it saves your verdict on the line; the request is decided when you approve or reject it.
When a request comes back to your step after a rollback or a revision, the verdict you gave a line last time still stands — “Your answer when this step was last asked stands”, followed by it — and Change it is still offered beside it, so you can replace it.
Approving from the record itself
A record with an approval open on it — a requisition, an asset transfer, a work order move — shows its chain under Where it has got to on its own screen too, and where the current level is yours it offers the same answers there: Approve, Forward, Send back for revision and Rollback where your step offers them, and Reject. Approve does not sign on the click: it opens a short panel saying “Your signature is recorded against your name and cannot be taken back. If this is the last step, what was asked for goes ahead.”, with A note (required where your workflow requires a remark, and not shown where it hides one), the file where the workflow asks for one, Approve it to sign and Cancel to back out. Forward, Send back for revision and Rollback open the full decision dialog on that answer. A step somebody forwarded says so under it on the chain — “Forwarded by Meera Iyer to Arjun Rao”, with the date and the reason they gave — so a signature by somebody the step never named can be explained. Under the chain, Rollbacks and revisions lists every time any request about the record went backwards or came forward again, oldest first — for example “Meera Iyer rolled it back from Level 2”, “Arjun Rao sent it to Priya Nair for revision from Finance check”, “Priya Nair sent it again”, each with its date and the note that went with it. A resubmission also says what changed — Changed: and the fields — or Nothing was changed. The same list appears under the chain in the decision dialog. While an approval on a record is open, the record is held whole: it cannot be edited, moved or deleted until the approval is decided, and its list marks it with a lock and an Approval column naming the approval. A second request of a different kind on the same record is refused for the same reason. A request with its initiator for revision still holds the record.The chain
Each step of the chain says in words where it stands:Acknowledging a request
Click a row on Asked of you. The dialog shows the request — Asked by, Step, Raised by and Site, then what would change and the record itself — who asked you and what they want checked, and reminds you that you are not approving it.Your own requests


There is no way to raise a rejected request again from here. A rejection is final; raise a new one where the first was raised.
Correcting a request and sending it again
A request sent back for revision goes to its initiator — whoever raised it, or the author of the record where somebody else sent it on their behalf — and only they may correct it, send it again or withdraw it. A colleague who sent a request about your record can follow it but is offered neither button. The dialog opens with what the approver asked, in their words: for example “Arjun Rao sent this back to you for revision”, with the date and their note. Edit and resubmit — on the dialog, or as a button on the row — reopens the request where it was made, filled in with what it asked for:
Every editor has Note to the approvers (“What you changed, and why — optional”) and Send it again. Once it has gone, Sent again for approval says “It has gone back to the approver who asked for the change. The approvals given before them stand, and you are told when it is decided.” The approver sees it with a resubmitted badge, with what they asked for and your note beside it, and the trail records what you changed — or that nothing was.
Bulk actions
Tick rows (or Select all) and a bar appears at the bottom. Each button says how many of the selection it will act on, for example Approve 3, so you can see before you press what it will leave alone.
After a bulk action the bar reports how many were done, how many were refused and why.
What can carry an approval
Anything your organisation has put a workflow in front of. A workflow guards one action — Create, Edit, Move between statuses or Delete — on one kind of record, and can branch by amount, category or site. Typical uses:
The same actions apply whatever the record. What differs is what each workflow was set to guard and who it names at each step. Workflows are built under approval workflows.

