Catalog · Guide
Build an approval chain
Each application and each group carries its own ordered steps. Add as many as the decision needs, or none.
01 One chain per item
Every application and every group has its own chain. Steps run in sequence. Each approver is emailed a link straight to the decision and can leave a comment on either outcome.
02 Choose who approves each step
Each step is one of five things: the requester’s manager, their manager’s manager, a third level up, the moderator of the application or group, or a named person or any direct member of a named group. Mix them in any order.
03 There are no approver lists to keep
Manager steps are read from your Microsoft directory as each step becomes the current one, and the approvers it finds are then recorded on that step. A reorganization changes who approves what for every step not yet reached. A step already in progress keeps the approvers recorded on it.
04 When someone has no manager
If the requester’s management chain is shorter than a step asks for, that step is cleared automatically and the reason is recorded. If your organization prefers, the request is blocked instead. It is one setting, made once.
05 Changing a chain later
Editing an item’s chain, moderator, install group or assignment target cancels the item’s open requests. Each requester is told why and invited to ask again, and you are warned how many requests are affected before you save.