Approvals inbox
All decisions that wait for you, in one list. Approve, reject or send back with a reason.
This page applies to every stage.
IDK templates: IDK-07, IDK-08
Page in the app: /p/{projectId}/approvals
How an approval runs
Nobody can approve their own request.
- Request. Someone asks for a status change.
- Rule check. The app finds the steps and people the rules require.
- Review. Each person decides in turn, or together when the rule says so.
- Done. The status changes. The decision is logged.
Project manager guide
Keep decisions moving, so that no status change waits for a person who is away.
- Clear your queue.
- Do now: Open the inbox. Read the item and its history, then approve, or reject with a short reason.
- Why: A waiting approval blocks the next status and the people who depend on it.
- The app checks: Nobody approves their own request. An approval that is overdue escalates to the executive sponsor.
- Next: Set a delegate before you go on leave.
- Delegate before you leave.
- Do now: Open Delegations. Pick the person, the dates and the approvals they may handle.
- Why: Work continues while you are away.
- The app checks: The audit log shows both the delegate and the original approver.
- Next: Check the approval rules.
- Know the rule.
- Do now: Open Approval rules to see who must approve each object type, and in which order.
- Why: You can ask the right people early.
- The app checks: Steps run in order, together or as a quorum. Some rules can be tuned for the project.
- Next: Return to your inbox.
How to do it
- Open the item. Read the fields and the history first.
- Decide. Approve, or reject with a short reason.
- Away? Set a delegate so work does not stop.
Good to know
- A decision on a gate, a cutover plan or a transport may ask you to sign in again with multi-factor authentication.
Related topics
Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.
Last updated: