App Requisition

App requisition automation rules

Admins will be able to set up multiple automation rules to apply for different license approval processes followed within the organization. 


These rules can be set up in a way where different request conditions will trigger a different approval workflow


For instance, if an organization follows a different workflow for each department, different rules can be set up for each department such that it goes through a different approval process. Or if there’s a different approval process for apps that are already managed by the organization and apps that need to be newly procured, a different approval process can be set up


Automation rules allows you to do this using two important components - ability to set up conditions for each rule, and configuring different approvers for each rule


Each rule can have two sets of conditions - check whether the application is already used by the org or not, and more specific criteria such as the requester’s department, designation, reporting manager, or the specific application requested. This helps create very specific approval workflows that apply to each request that’s raised



Each rule can also have its own set of approvers that will need to take an approval action for every request that fits the conditions of that rule. For example - a request raised by a member of the sales team can have the most relevant members approve that request, say the employee’s reporting manager, the head of sales, and then the IT admin 


Can’t find what you are looking for? Let us help you!

App Requisition

Modified on Sat, 31 Dec 2022 at 05:52 PM

App requisition automation rules

Admins will be able to set up multiple automation rules to apply for different license approval processes followed within the organization. 


These rules can be set up in a way where different request conditions will trigger a different approval workflow


For instance, if an organization follows a different workflow for each department, different rules can be set up for each department such that it goes through a different approval process. Or if there’s a different approval process for apps that are already managed by the organization and apps that need to be newly procured, a different approval process can be set up


Automation rules allows you to do this using two important components - ability to set up conditions for each rule, and configuring different approvers for each rule


Each rule can have two sets of conditions - check whether the application is already used by the org or not, and more specific criteria such as the requester’s department, designation, reporting manager, or the specific application requested. This helps create very specific approval workflows that apply to each request that’s raised



Each rule can also have its own set of approvers that will need to take an approval action for every request that fits the conditions of that rule. For example - a request raised by a member of the sales team can have the most relevant members approve that request, say the employee’s reporting manager, the head of sales, and then the IT admin 


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article