SharePoint HTML views: build an interactive list interface
SharePoint Online

SharePoint HTML views: build an interactive list interface

by HubSite 365 about Daniel Anderson [MVP]

A Microsoft MVP 𝗁𝖾𝗅𝗉𝗂𝗇𝗀 develop careers, scale and 𝗀𝗋𝗈𝗐 businesses 𝖻𝗒 𝖾𝗆𝗉𝗈𝗐𝖾𝗋𝗂𝗇𝗀 everyone 𝗍𝗈 𝖺𝖼𝗁𝗂𝖾𝗏𝖾 𝗆𝗈𝗋𝖾 𝗐𝗂𝗍𝗁 𝖬𝗂𝖼𝗋𝗈𝗌𝗈𝖿𝗍 𝟥𝟨𝟧

SharePoint users can pair a Copilot-created HTML view with an interactive form to work through list tasks in a focused interface.

Key insights

  • The example puts new starters in one panel and the selected person's onboarding checklist in another.
  • The HTML view includes search, filters, progress information, and task actions such as Mark done and Update.
  • A reusable checklist form can be saved in the Site Assets library and run through a skill.
  • The skill can open a named person's checklist or present a picker when no name is supplied.
  • The list and sample records in the onboarding example are demo data.

SharePoint HTML views can turn a list into a focused work interface, combining a tailored display of list data with actions for updating records. This approach is relevant to SharePoint site owners, makers, and teams that want to guide people through a specific list-based process such as onboarding. Daniel Anderson [MVP] demonstrates the approach with an onboarding tracker, a custom HTML view, and an interactive checklist form.

What it does

A conventional list view presents records and columns; the demonstrated HTML view instead organizes a work task around a selected person. The sample interface, called Onboarding Desk, places new starters in a left panel and the selected starter’s checklist in a right panel. Its stated purpose is not to summarize data with charts, but to help someone find a starter, see progress, and update tasks.

The view includes a search box, progress information, and filters for task status and owner team. In the example, the owner-team filter offers All, People and Culture, IT, Manager, Payroll, and Facilities. Tasks that are not marked Done can have Mark done and Update actions, while a Work through checklist button connects the selected starter to a Copilot checklist experience.

The second part is an interactive form for updating multiple checklist tasks. The form can be created as a reusable template rather than being tied to one person. The example then saves that form in the Site Assets library and creates a skill to run it. The list remains the place where the onboarding records and task updates live; the HTML view and form provide a more guided way to work with them.

Who it is for and what you need

This pattern suits teams whose users need to complete a repeated process against SharePoint list records. The example uses onboarding, but the practical idea is to design around the work a person must do rather than reproduce every list column on screen. Site owners or makers can start with a list, a description of its structure, and a clear plan for the interface and form.

In the demonstration, the list structure is planned in a Markdown file that describes the solution and information architecture. Copilot in SharePoint is asked to review that plan and implement the list. The records are sample data, so the example illustrates the design and interaction rather than a production onboarding setup.

The interface and task flow depend on the list and the prompts used to create them. For a real process, decide which people, tasks, statuses, and updates the experience needs to handle. The example does not establish a particular license or tenant rollout condition, so treat the demonstrated steps as an illustration of the workflow rather than a promise that every environment has the same controls.

How it works

  1. Plan the list. Describe the list structure and information architecture in Markdown. Ask Copilot to review the plan and build the list. The example uses an onboarding tracker with demo entries.
  2. Describe the view’s purpose and layout. Ask Copilot to create an HTML view called Onboarding Desk. The prompt explicitly says it is not a dashboard and requests two panels: new starters on the left and the selected person’s checklist on the right.
  3. Specify interactions. The example prompt asks for search, team filters, progress, task status, and actions for tasks that are not Done. It also asks for a Work through checklist button beside the selected person’s name. Check the generated view to see whether its controls behave as intended.
  4. Create the interactive checklist. Ask Copilot to build an onboarding checklist form as a reusable template. In the example, Copilot asks a clarifying question, then presents a way to choose a starter and load that person’s tasks.
  5. Save and run the form as a skill. The demonstration saves the completed template in the Site Assets library and creates an onboarding-checklist skill. It tests the skill by choosing a person, changing task statuses and notes, and sending the changes to Copilot to update the list.
  6. Support both entry paths. Configure the skill so a supplied name opens that person’s checklist directly. When the user starts the skill without a name, it presents a picker; selecting a person then opens that checklist.

This last distinction makes the experience useful both from the list view, where a person is already selected, and when someone starts with a general request. The demonstration also tests opening the checklist by naming a starter in natural language, rather than relying only on the view’s button.

Limitations and alternatives

The example is a working demonstration built with sample data, not a documented deployment recipe for every SharePoint list. The result depends on how the list, view prompt, form template, and skill are configured. Test the generated interface against the real records and task updates your process requires before directing users to it.

Copilot asks a clarifying question while the form is being built, and the skill behavior takes some refinement: it must distinguish between a request with a person’s name and one without. That is a useful design check. Test both paths, confirm that the intended starter is loaded, and verify that edits return to the correct list items.

The shown alternative to the custom interface is working directly with the list and its records. The HTML view adds a task-oriented presentation, while the interactive form offers a guided way to update several checklist items. Keep the underlying list and its data structure clear, since both experiences are built around those records.

Sources

Frequently asked questions

Can a SharePoint HTML view update list items?

In the onboarding example, the view has actions for tasks, and its checklist form sends changes to Copilot to update the list.

Can I reuse a SharePoint interactive checklist form?

The example creates the checklist as a reusable template, saves it in the Site Assets library, and runs it through a skill.

How can a checklist skill select a person?

A user can supply a person's name to open that checklist directly. Without a name, the skill presents a picker.

What does the SharePoint onboarding HTML view include?

The example has a new-starters panel, a selected person's checklist, search, team and status filters, progress information, and task actions.