SharePoint HTML list views are interactive dashboards that Copilot in SharePoint builds directly on a list or library. You describe who the view is for and what they need to see, and it appears next to All Items, working from the live data in that list.
A standard view is good for working through rows. It’s less useful for the project lead who wants to know what’s stuck, or the safety manager who needs the worst findings first. I ran five scenarios on sample data to see how far these views go, and the answer is a long way, right up to the moment someone needs to change a value.
Before you start
- Copilot in SharePoint. You build these views through Copilot in SharePoint, so the builder needs a Microsoft 365 Copilot licence.
- The feature in your tenant. Zach Rosenfield from Microsoft listed Frontier tenants from 29 October 2026 and everyone else “in the coming weeks” in his announcement video. If you don’t see Dashboard under Add view, it probably hasn’t reached you yet.
- Data in columns. The view reads list columns. Anything sitting inside a file has to be pulled into a column first.
In replies on that same video, Zach says building a view doesn’t use Copilot credits and only the person creating it needs a Copilot licence, so viewers don’t. I couldn’t find either point in Microsoft’s documentation yet, so check them before you put them in a business case.
How to create an HTML list view
There are two ways in, and both end up in the same place.
From a prompt:
- Open the list and open Copilot in SharePoint.
- Say what the view is called, who it’s for and what they need to see.
- Refine it with follow-up prompts until it suits that person.
My first prompt started “Create a HTML dashboard called Rollout Status for the project lead.” The result was fully interactive and already wired to the data.
From Add view:
- Open the list and select Add view.
- Choose Dashboard.
- Give the view a name and select Create.
Copilot takes the name and writes the prompt for you. I called mine Rollout Status Update, and it wrote “Create a new view containing live interactive dashboard named Rollout Status Update that shows what’s happening and what needs attention.” It then asked which signals should count as needing attention. I picked gaps and past due target dates, and it carried on.
Take the Add view route when you’re not sure what to ask for, because Copilot writes the first prompt from the view name. A list can hold several HTML views, so I ended up with both, each aimed at a different audience.
Refine the view with plain follow-up prompts
The first version is a draft. One follow-up prompt made Training by Department full width with a coloured KPI card per department, and added filters for Department, Stage and Team plus a search box. The filters, sorting and search all worked, and searching for Procurement narrowed the table straight away.
Layout changes are just as easy. My new starter checklist came back grouped by person, and one prompt turned it into an accordion with each person collapsed by default.
Five HTML list views I built
| Scenario | Who it’s for | What the view does | What I learned |
|---|---|---|---|
| Copilot rollout tracker | Project lead | KPI cards, filters, search, a needs-attention toggle | One list can carry different views for different audiences |
| Friday status report | Project team | What changed in seven days, what’s blocked, what’s overdue | The view is live, so nobody rebuilds it on Friday |
| New starter onboarding | HR | Tasks grouped by person, overdue items flagged | Layout can change with one prompt |
| Inspection reports | Safety manager | Open actions grouped by site, highest severity first | PDFs need metadata first |
| Facilities requests | Whoever triages them | Urgent and unassigned requests | Views stop at reading the data |
The Friday status report is the one I’d copy first. The prompt asked for a view called Friday Status that summarised what had changed in the last seven days, then showed overdue and blocked items. The view is live: it showed four blocked items, and changing one item from In Progress to Blocked took the count to five. No export.
Name one reader and check the columns before you generate anything
The inspection library is where people will get stuck. It held 20 PDFs with no metadata at all, and a view can’t report on what’s trapped inside a document.
So the order matters. Copilot in SharePoint added autofill columns for the site, inspection date, severity, open actions, owner and follow-up due, six in all, and filled them in from the files. Only then did I ask for the view: “Create a HTML dashboard view called Open Actions for the safety manager. Group by status, put the highest severity first, and call out anything with no action owner.” When Copilot checked, I changed it to group by site and order by severity.
Check a handful of autofilled values against the documents before anyone relies on that view. A dashboard makes a wrong value look official, and in a safety context you want to catch it first.
The view can only group, sort and flag what’s in a column, so decide which columns that reader needs and fix those first. Then name the reader in your prompt. “For the safety manager” gives Copilot one person to design around. If the project lead wants something different, build them a second view on the same list.
The limit: you can’t edit inside a view yet
At the time of recording, you can’t edit or create items inside an HTML view. That may change, but plan for it now.
You can get close. On the facilities list I asked Copilot to “add an edit link to each request that opens its item form and add a link to create a new request.” I hadn’t tried this before recording, and it worked. Create new request opened the new item form, and Edit opened the item in a different tab. The editing happens in the standard SharePoint form, outside the view.
So use HTML views for reading, triaging and reporting. If someone’s job is to work through a long queue and update each item, give them a standard view, which is still there next to your new one.
How is this different from an HTML page or dashboard file?
Earlier options gave you a live dashboard built from a list and standalone SharePoint HTML pages in the Site Pages library. Both are still useful, particularly a page that pulls several things together. An HTML list view lives on the list itself, in the view picker, so people find it where they already go to look at the data. There’s no separate link to share or page to find.
Frequently asked questions
Do HTML views work on document libraries as well as lists? Yes. I built one on a library of inspection PDFs. The view works from the library’s columns, so add metadata first if the detail is sitting inside the files.
Can one list have more than one HTML view? Yes. My rollout tracker ended up with two, one started from a prompt and one started from Add view, and both sat in the view picker alongside the standard views.
Can I restyle a view after it’s built? Yes, by prompt. The KPI cards and the accordion in my demo both came from follow-ups, with no code to touch.
