--- title: Add sequential approval rounds to an Approval Policy description: Chain multiple rounds of approval in an Approval Policy so a request moves through manager, security, and finance (or whichever groups you need) one at a time, with automatic cancellation if any round is rejected. --- [Skip to content](https://help.siit.io/how-to-add-sequential-approval-rounds-to-an-approval-policy#main-content) [![Logo\_Siit\_Full\_White](https://help.siit.io/hs-fs/hubfs/Logo_Siit_Full_White.png?width=70&height=33&name=Logo_Siit_Full_White.png)](https://help.siit.io/?hsLang=en) - [Help Center](https://help.siit.io/) - [Docs](https://docs.siit.io/) - [API reference](https://developer.siit.io/api-reference/authentication) - [Changelog](https://www.siit.io/changelog) Open main navigation Close main navigation - [Help Center](https://help.siit.io/) - [Docs](https://docs.siit.io/) - [API reference](https://developer.siit.io/api-reference/authentication) - [Changelog](https://www.siit.io/changelog) How can we help? - There are no suggestions because the search field is empty. 1. [Help center](https://help.siit.io/?hsLang=en) 2. [Request and Service Management](https://help.siit.io/request-and-service-management?hsLang=en) 3. [App access](https://help.siit.io/request-and-service-management?hsLang=en#app-access) # Add sequential approval rounds to an Approval Policy ## Chain multiple rounds of approval in an Approval Policy so a request moves through manager, security, and finance (or whichever groups you need) one at a time, with automatic cancellation if any round is rejected. ### What this guide helps you achieve - Add more than one round of approval to an Approval Policy - Control the order rounds run in - Understand what happens when a round is rejected - Know exactly when provisioning fires ### Where to find it `Settings → Approval Policies → [Policy] → Add round` ### How it works - Round 1 runs first. Once every approver in Round 1 signs off, Round 2 starts automatically. - If Round 1 is rejected, Round 2 (and any round after it) is cancelled. Nothing downstream is ever triggered. - App Access provisioning is held until the final round is approved. As long as any round is pending, nothing is granted. ### Steps 1. Go to **Settings**, then **Approval Policies**, and open the policy you want to edit. 2. In **Round of approval 1**, click **Select approvers** and choose who signs off first (a specific person, a team, an inbox, or a dynamic role such as App owner). 3. Set the approver mode for that round (for example **All users**) to control whether every member of the group must approve or a single decision is enough. 4. Click **Add another round of approval** to add a second round. Siit labels it automatically to show the dependency, for example "Round of approval 2, triggered once round 1 is approved." 5. Repeat for as many rounds as the policy needs. 6. Click **Save**. *![CleanShot 2026-07-15 at 18.02.29@2x](https://help.siit.io/hs-fs/hubfs/CleanShot%202026-07-15%20at%2018.02.29@2x.png?width=670&height=535&name=CleanShot%202026-07-15%20at%2018.02.29@2x.png)* ### Example use case A Salesforce admin Role needs sign off from the App owner, then Finance, since the license carries a cost. The policy is configured with two rounds: Round 1 is the App owner, Round 2 is Finance, triggered only once Round 1 is approved. If the App owner rejects the request, Finance never sees it. ![image (1)](https://help.siit.io/hs-fs/hubfs/image%20(1).png?width=670&height=1088&name=image%20(1).png) ### Common pitfalls - **Adding rounds in the wrong order.** Rounds run strictly in the order they appear in the policy, so double check the sequence before saving. - **Expecting partial provisioning.** Access is not granted after an early round approves. It only fires once every round in the policy has signed off. ### Best practices - Reserve multiple rounds for higher risk apps or higher cost access. A single round is still the right call for low risk, high volume requests. - Keep the round count reasonable. Each extra round adds latency for the requester, so only add one when a distinct stakeholder genuinely needs to weigh in. ### Availability Pro plan. ### Frequently asked questions **What happens if I only need one approver?** You don't have to add a second round. A policy with a single round behaves exactly as it did before this update. **What happens if a round is rejected?** Every round still waiting behind it, is cancelled automatically, and the request is marked rejected. Approvers further down the chain are never notified. **When does app access actually get provisioned?** Only after every round in the policy has been approved. Provisioning never runs partway through a chain. - [Getting started](https://help.siit.io/getting-started?hsLang=en#main-content) - [For Admins](https://help.siit.io/getting-started?hsLang=en#for-admins) - [Employee Guides](https://help.siit.io/getting-started?hsLang=en#employee-guides) - [Request and Service Management](https://help.siit.io/request-and-service-management?hsLang=en#main-content) - [Request](https://help.siit.io/request-and-service-management?hsLang=en#request) - [Email](https://help.siit.io/request-and-service-management?hsLang=en#email) - [Service catalog](https://help.siit.io/request-and-service-management?hsLang=en#service-catalog) - [SLAs](https://help.siit.io/request-and-service-management?hsLang=en#slas) - [App access](https://help.siit.io/request-and-service-management?hsLang=en#app-access) - [AI & Agents](https://help.siit.io/ai-agents?hsLang=en#main-content) - [Overview](https://help.siit.io/ai-agents?hsLang=en#overview) - [Setup](https://help.siit.io/ai-agents?hsLang=en#setup) - [Use cases](https://help.siit.io/ai-agents?hsLang=en#use-cases) - [Automations and Workflows](https://help.siit.io/automations-and-workflows?hsLang=en#main-content) - [Getting started](https://help.siit.io/automations-and-workflows?hsLang=en#getting-started) - [Use cases](https://help.siit.io/automations-and-workflows?hsLang=en#use-cases) - [Integrations](https://help.siit.io/automations-and-workflows?hsLang=en#integrations) - [Reporting and Analytics](https://help.siit.io/reporting-and-analytics?hsLang=en) - [Integrations](https://help.siit.io/integrations?hsLang=en#main-content) - [Communication](https://help.siit.io/integrations?hsLang=en#communication) - [HRIS](https://help.siit.io/integrations?hsLang=en#hris) - [Ticketing](https://help.siit.io/integrations?hsLang=en#ticketing) - [Knowledge base](https://help.siit.io/integrations?hsLang=en#knowledge-base) - [Identity Provider](https://help.siit.io/integrations?hsLang=en#identity-provider) - [Device Management](https://help.siit.io/integrations?hsLang=en#device-management) - [Knowledge Base Management](https://help.siit.io/knowledge-base-management?hsLang=en) - [Admin, Security & Workspace](https://help.siit.io/admin-security-workspace?hsLang=en#main-content) - [Workspace Settings](https://help.siit.io/admin-security-workspace?hsLang=en#workspace-settings) - [SSO (SAML)](https://help.siit.io/admin-security-workspace?hsLang=en#sso-saml) - [SCIM & Provisioning](https://help.siit.io/admin-security-workspace?hsLang=en#scim-provisioning) - [People & Directory](https://help.siit.io/admin-security-workspace?hsLang=en#people-directory) [![Siit\_Logo\_Dark](https://help.siit.io/hs-fs/hubfs/Siit_Logo_Dark.png?width=140&height=67&name=Siit_Logo_Dark.png "Siit_Logo_Dark")](http://siit.io) Copyright © 2025, Siit SAS