Workflows
      Back to home
      1. Knowledge Base | Siit Help
      2. Workflows

      Approval Request Management

      What is an approval request, and why is it important?

      In a corporate environment, certain actions — such as accessing an app, ordering new hardware, or requesting time off — often require prior validation. This validation ensures that the right people are aware of the request, confirm its legitimacy, and approve it before resources are allocated or changes are made.

      Approvals help businesses:

      • Maintain control over costs and security,

      • Ensure alignment with internal policies,

      • Improve accountability across teams.

      Siit includes a powerful and flexible Approval Request feature that fits seamlessly into your automated workflows. Whether it’s granting app access, ordering equipment, or processing a specific employee request, Siit enables you to trigger automated approvals to the right people — at the right time.

       

      How to set up an approval in your workflow?

      The Approval is an action that can be added to any requests workflow via the "Select approver" action.

      1. Add an Approval action at the point where validation is needed.

      Once added, it will automatically present the two branches for the "approved" or the "rejected" option which will allow you to configure follow up actions according to the choice made.

       

      You can set up single or multi-level approval sequences.



      2.     Define the approver

        • Use dynamic fields like “Manager” or “App Owner” to automatically pull the right person from your data.

        • Or, assign a fixed employee as approver 

       

      3.    Set up reminders to ensure follow-up if no action is taken.


      In case the approval is not given after a certain time (from 1 day to several weeks), in order to prevent the rest of the flow to pursue, you can set up automatic reminder straight from the approval configuration:  


      How to approve?

      Approver will simply have to review the request he got notify for on Slack or Teams and Accept 👍 the request or ❌ Reject accordingly. 

       

      Example: App Access Request with 3-Level Approval

      Let’s say an employee requests access to a paid app like Salesforce or Asana. The company wants to make sure:

      1. Finance confirms that the cost is acceptable,

      2. The Manager confirms the employee really needs the tool,

      3. The App Owner (usually IT) grants access.

      This setup ensures that each stakeholder is involved only when relevant, and the request is not escalated unnecessarily if blocked early in the process.