Every request you make at work now lands in the same place.
Organizations run on requests. Time off. A trip. An expense claim. A new laptop. Access to a system. A purchase order. Each one has its own form and its own SharePoint list behind it, and each one is somewhere slightly different.
The new List Approvals widget gathers all of them into one screen. What you asked for, what is waiting on you, and what has already been decided. No searching, no bookmarks, no asking a colleague where the form lives.
Every kind of request, in one view
My requests is where your own requests live, whatever kind they are. A travel request and an expense claim sit in the same view, each with its status in plain words: Requested for the one you sent, Not submitted for the draft you started this morning. The tab carries a count, so you can see from the header that two things are in flight.
Every row tells you the same four things: what the request is, which list it came from, when you submitted it, and where it stands. That is enough to answer “did that go through?” without opening anything.
Recently approved answers that question before you ask it. A request that has just been decided appears right underneath your open ones, so you see the outcome where you were already looking, without going to History to check.
History keeps the full record: the decision, the date and the person who made it. Useful the next time someone asks when exactly that trip was approved.
Start a request in one click, and send it when it is ready
The orange button in the corner starts a new request. Connected to more than one list? It opens a short menu with each list by name and its own icon. People pick “Travel requests” or “Expense Claims” the way they would say it out loud, and the right form opens. Nobody has to know which SharePoint site it lives on, or keep a link to it.
A new request starts as a draft. It sits in My requests as Not submitted until you decide it is ready, so you can fill in the form now and send it once you have the receipt or the final price.
When you do send it, the Submit for approval dialog is where it gets its direction. Give it a title and add any context in the Details field. Depending on how that list is set up, you either choose the approvers yourself, with toggles for whether they respond in order and whether everyone has to respond, or you see the approvers your organization already decided on.
Your approvers are then notified through the Approvals app in Microsoft Teams, so the request reaches them where they already work. From that moment you can follow it in My requests, and open it to see exactly where it stands.
For the people who have to act, one entry point
To approve shows what is waiting on you, across every connected list. One tab instead of a mail search and three bookmarks. Open your board, glance at the tab, and you know. Empty means empty.
Click a request and the approval dialog opens with two columns. On the left: the status, the approval activity so far with names and faces, and who requested it and when. Underneath, a comment box for anything you want to say along with your decision.
On the right: the request itself, with the fields that matter for this kind of request. A travel request shows the reason for travel, the estimated hotel cost and the estimated airfare, each with its own explanation on hover. An expense claim shows the date, the category and the amount instead.
Approve or Reject, and you are done. No opening the list, no hunting for the item, no second tab.
Your own request looks like your own request
Open a request you submitted yourself and the same dialog fits that role. The status reads Submitted, there is no comment box, and the action available to you is Cancel request.
A small thing, and exactly right. Nobody is ever looking at an Approve button for their own travel plans.
Two screens to set up, and your SharePoint stays put
Setting up the widget is short. Open Configure Approvals, add the lists you want to offer, give each one a description so people know at a glance what it is for, and drag them into the order you want them shown.
Each list then gets a screen of its own: the site, the list, the title column, the URL of its request form, an audience so it only appears for the right people, and a notes field for whoever configures it next.
The same screen is where you pick the columns. Add the fields from that list that an approver actually needs, drag them into the order you want, and those are the fields that show up alongside every request. A travel request can show the reason and the costs. An expense claim shows something else entirely.
You also decide how much freedom the requester gets. Whether someone picks their own approvers when they submit follows the list configuration and the way that list is connected in the widget, and the widget administrator can adjust that per list whenever it needs to change.
The last piece is the form itself, and that one is yours. Point the widget at a form built with Microsoft Lists or with Microsoft Forms, whichever your team already works in, with the fields your process actually needs: a category, an amount, a currency, an attachment for the receipt. It opens in a dialog on the board, so people fill it in without going anywhere.
What they submit is stored in the SharePoint list behind that form. Your lists stay where they are, your flows keep running, and your permissions keep applying. The widget reads what is already there.
Approvals that fit in a minute
Approvals work best when they take about a minute. Someone asks, someone decides, everyone gets on with their day.
List Approvals is built for that minute, from both sides. The person asking finds the right form in one click, sends it when it is ready, and can see where it stands. The person deciding gets a notification in Microsoft Teams, finds everything waiting on them in one tab, and has enough on screen to say yes.
Ready when you are
List Approvals is live. An administrator adds it from the admin center, points it at the lists you already use, and it appears for the people it is meant for. No project, no migration.
In Bloom Hub it sits on the homepage of your digital workplace. With Bloom Elements it goes on any SharePoint page you choose.
Want to see it on your own lists? Book a demo.
