{"id":8678,"date":"2022-01-03T21:43:43","date_gmt":"2022-01-03T20:43:43","guid":{"rendered":"https:\/\/nboldapp.com\/?p=8678"},"modified":"2025-03-24T07:09:10","modified_gmt":"2025-03-24T06:09:10","slug":"multilevel-approval-process-with-power-automate","status":"publish","type":"post","link":"https:\/\/nboldapp.com\/fr\/multilevel-approval-process-with-power-automate\/","title":{"rendered":"Processus d'approbation \u00e0 plusieurs niveaux avec Power Automate"},"content":{"rendered":"

Whether you need to approve your annual budget plan or an updated sales deck sent to your key account, getting things approved is an essential part of almost each organizational process. And often this process requires multiple steps of sharing docs, organizing meetings, and waiting for responses from various stakeholders. With Connecteur Power Automate<\/a> flows you\u2019re able to automate your approval process, save working hours and boost your team productivity. We already discussed how to build simple Power Automate flows with approvals<\/a>. And in today\u2019s article, we will walk you through how to build workflows in Power Automate with multiple approvals.  <\/p>\n\n\n\n

<\/div>\n\n\n\n

Why do you need multiple approvals? <\/h2>\n\n\n\n

Suppose you\u2019re a project manager and you need to approve project files that your team share during their daily activities. Then you can build a simple Power Automate flow<\/a> with only one step approval process. In this case, you will get a notification each time your team members create a new file or SharePoint item.  <\/p>\n\n\n\n

But sometimes, an approval workflow requires a pre-approval before the final approver is required to sign off. For instance, before a general project plan is sent to the stakeholders, it must be approved by the project manager.  <\/p>\n\n\n\n

\"Multi<\/figure>\n\n\n\n
<\/div>\n\n\n\n

One more scenario is related to the high-cost expenses or invoices. For example, you have an approval policy that requires a pre-approval stage for each invoice over 10000$ before sending it to your Finance department.  <\/p>\n\n\n\n

Finally, let\u2019s say you would like to control and protect your workspace and limit team creation<\/a> in Microsoft Teams. In this case, you can build a multilevel approval workflow when your admin and operational director receive approval requests each time a project manager wants to create a new project team. <\/p>\n\n\n\n

The use cases are endless and with Power Automate and its no-code solution, you\u2019re able to build any automation flow that streamlines your approval process. And now let\u2019s delve into the step-by-step examples.  <\/p>\n\n\n\n

<\/div>\n\n\n\n
\n

Livre blanc : Gestion de projet avec Microsoft Teams<\/h4>\n\n\n\n

Apprendre \u00e0 utiliser Microsoft Teams pour une gestion de projet efficace<\/p>\n\n\n

\n\t\t\t\n\t\t\t\t
\n\t\t\t\t\tT\u00e9l\u00e9charger<\/strong><\/span>\n\t\t\t\t<\/div>\n\t\t\t<\/a>\n\t\t<\/div><\/div><\/div>
\"Power<\/figure><\/div>\n\n\n\n
<\/div>\n\n\n\n

Set up multiple approvals in Power Automate <\/h2>\n\n\n\n

Let\u2019s create a flow in Power Automate to set up multiple approvals. Suppose you\u2019re a project manager and your project team is preparing a project plan. To finalize the project plan, you need to receive approval from various stakeholders. But before sending the approval request to them, you would like to revise the project plan yourself. Let\u2019s see how you can foster and automate this multilevel approval process in Power Automate.  <\/p>\n\n\n\n

First, create a SharePoint list where your team can attach files related to your project planning and add metadata with key information. For instance, dates, responsibilities, status, etc.  <\/p>\n\n\n\n

\"project<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Next, go over the Power Automate and start a new flow. Choose the SharePoint trigger \u201cWhen a new item is created<\/em>\u201d and choose the right SharePoint site.  <\/p>\n\n\n\n

\"multistage<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Then add an action from the Approval app \u201cStart and wait for the approval<\/em>.\u201d Here you can choose multiple options, such as first to respond<\/em>, everyone must approve<\/em>, etc. At this step, you will receive a notification each time a new item is created by your team in your SharePoint item.  <\/p>\n\n\n\n

\"multistage<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Now you need to add the second step of the approval process. Add \u201cOui\/Non<\/em>\u201d conditions, and type: \u201cOutcome is equal to Approve.\u201d If yes, you start a new approval process. Repete actions from the previous step and choose the right people, for example, your stakeholders. If the first approver has rejected the request, send the notification to your team with comments and details about what must be corrected.  <\/p>\n\n\n\n

\"multistage<\/figure>\n\n\n\n
<\/div>\n\n\n\n

With this simple flow, each new file related to the project plan will be sent to your stakeholders only after it is approved by the project manager. You can scale this approval workflow and add as many steps as required according to your operational scenarios.  <\/p>\n\n\n\n

\"multistage<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Automatically update approval status indicator   <\/h2>\n\n\n\n

Now, let\u2019s update our flow. Remember, we have a SharePoint list with the status column? In Power Automate you\u2019re able to set up the multilevel approval workflow and update the SharePoint column automatically. So, if a new item is approved by all approvers, the status column will automatically change to Approved. By using this flow, you can easily track the approval process through your SharePoint lists. Let\u2019s see how it works.  <\/p>\n\n\n\n

We begin with the same SharePoint trigger \u201cWhen a new item is created<\/em>.\u201d Then add an action \u201cUpdate item<\/em>,\u201d choose the right SharePoint site, add the dynamic content from the trigger to the related fields. And now, update the approval status, by choosing an option. In this case, we would like to update the approval status to \u201cPending\u201d each time a new item is created in the SharePoint list.  <\/p>\n\n\n\n

\"sharepoint<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Then you can repeat all the actions from the previous workflow where we have added the multilevel approval process. But in this case, we will update our flow by adding actions \u201cUpdate item<\/em>.\u201d So, after the last \u201cOui\/Non<\/em>\u201d conditions are done (when the last approvers receive a request) add an action \u201cUpdate item<\/em>.\u201d  <\/p>\n\n\n\n

If yes, we would like to update the Status column to Approved. If not, we update the status to Rejected.  <\/p>\n\n\n\n

\"sharepoint<\/figure>\n\n\n\n
<\/div>\n\n\n\n

With this flow, you\u2019re able to not only automatically send the approval requests, but also to update your SharePoint lists to easily track the approval process.  <\/p>\n\n\n\n

<\/div>\n\n\n\n

Add dynamic approvers selection for multilevel approval in Power Automate<\/h2>\n\n\n\n

Now, let\u2019s discuss one more use case. Let\u2019s say you\u2019re a manager in the procurement department. Your team works with multiple suppliers, and they need to order the materials required for packaging and shipping on a permanent basis. To issue a new request, your colleagues create a new item in your \u201cProduction support items\u201d list which reflects the name of the purchase, purpose, supplier, expenses, expected days of delivery, and the responsible person for a new order.  <\/p>\n\n\n\n

Apprendre<\/a> how to create a team with SharePoint list already at place<\/h4>\n\n\n\n
\"SharePoint<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Each new request must be approved by your financial department before sending the order to the supplier. At the same time, you would like to add an additional approval step for each request where the expenses are more than 10 000$. Moreover, this request must be sent to the requester\u2019s manager that is responsible for several types of purchases.  <\/p>\n\n\n\n

So, what do we have? We need to build the multiple stage approval process, with a dynamic listing of approvers and additional conditions related to the amount of expected expenses. Well, it\u2019s an easy deal with Power Automate.  <\/p>\n\n\n\n

We start with the same trigger for the SharePoint item. Then add a new \u201cOui\/Non<\/em>\u201d condition for the amount of expenses. Add dynamic content from your SharePoint lists and set up a new condition. In our case, it\u2019s \u201cExpenses is greater than 10000\u201d <\/p>\n\n\n\n

\"multistage<\/figure>\n\n\n\n
<\/div>\n\n\n\n

If no, we need only a one-step approval request and we are sending the request to our financial department. You already know how to do it.  <\/p>\n\n\n\n

\"multistage<\/figure>\n\n\n\n
<\/div>\n\n\n\n

But if the expenses are over 1000$ we would like the request to be approved by the requester\u2019s manager. To do this, add the action \u201cGet manager<\/em>.\u201d Into \u201cUser\u201d files, add a requester\u2019s email using the dynamic content from the SharePoint list.  <\/p>\n\n\n\n

\"multistage<\/figure>\n\n\n\n
<\/div>\n\n\n\n

And now you are able to repeat your multilevel approval process that will be sent to the right manager on the pre-approval stage.  
 <\/p>\n\n\n\n

\"multistage<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Control team creation at scale with the multilevel approval process <\/h2>\n\n\n\n

Finally, let\u2019s delve into another scenario. Suppose you\u2019re an operational director and you would like to control your Microsoft Teams environment to boost your teams\u2019 productivity and streamline your internal processes. Indeed, when your workers can create multiple teams, you may face a mess in your Teams environment with unused and duplicated teams which leads to L'\u00e9talement des \u00e9quipes<\/a>. When you work in a big team, the process of team creation may lead to chaos and additional charge on your IT.  <\/p>\n\n\n\n

In fact, there are many ways on how to restrict users from team creation in Microsoft Teams. Today we describe how to do it with Power Automate workflows. For instance, you can control team creation by using Microsoft Forms. With this simple flow<\/a>, you will get an approval notification each time a user submits the team creation form. Moreover, a team creation process will start automatically. <\/p>\n\n\n\n

\"demande<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Read more about how to build the flow ici<\/a>.  <\/strong><\/h4>\n\n\n\n

But there is a more efficient way. With
Mod\u00e8les de collaboration<\/a> technology you are able to structure your working environment and bulk create teams from your own Template Catalog. Moreover, with additional governance settings, you can easily set up the approval workflow for specific templates. Sounds great? Let\u2019s see how it works.  <\/p>\n\n\n\n

Using the nBold app from the Microsoft Teams store you can create your own Template Catalog for any use case. Create Project Management Template to be able to quickly get a team once a new project is coming. Build Key Account Template to get the same level of execution from one team to another, Crisis Management to quickly tackle any crisis, and so on.  <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Explore more Microsoft Teams use cases<\/a>. <\/p>\n\n\n\n

Next, during the template creation, you can set up an approval workflow. Choose an approver (e.g. your manager, Teams admin, etc.). Next time, once a user wants to create a new team from the template, the approver will get an actionable message with all the request\u2019s details.  <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
<\/div>\n\n\n\n

As soon as the request is approved, team creation will start automatically. Users will get a pre-built collaborative workspace with all the content, including:  <\/p>\n\n\n\n