A Microsoft MVP 𝗁𝖾𝗅𝗉𝗂𝗇𝗀 develop careers, scale and 𝗀𝗋𝗈𝗐 businesses 𝖻𝗒 𝖾𝗆𝗉𝗈𝗐𝖾𝗋𝗂𝗇𝗀 everyone 𝗍𝗈 𝖺𝖼𝗁𝗂𝖾𝗏𝖾 𝗆𝗈𝗋𝖾 𝗐𝗂𝗍𝗁 𝖬𝗂𝖼𝗋𝗈𝗌𝗈𝖿𝗍 𝟥𝟨𝟧
SharePoint Copilot interactive forms can be launched from a document library quick step or a home-page button, letting users review and submit changes without starting by typing a prompt. This approach is aimed at SharePoint users who need to complete a repeatable process against list or library data. Daniel Anderson [MVP] demonstrates the two launch methods using an overdue-document review as an example.
A Copilot interactive form presents relevant information and choices in a form-like experience, then sends the user’s decisions to Copilot for processing. In the example, a skill gathers documents that are overdue or need attention from a SharePoint compliance library. The resulting form lets a reviewer adjust dates or mark documents as expired.
The form is not simply an automatic update screen. After the user submits decisions, Copilot presents a confirmation step before making changes to the documents. That pause keeps a person involved in each run and gives the reviewer a chance to approve or stop the proposed updates.
The demonstration also uses a separate brand-and-theme skill to style generated HTML pages, views, or forms. That skill runs when the form is created, so the interactive experience can use styling consistent with the site. The example’s library and documents are sample data rather than a ready-made compliance solution.
This pattern is relevant to SharePoint site owners, makers, and teams that want to make a repeatable review process easier for end users to find. It depends on a skill configured to identify the right library and follow the intended process. The demonstration does not provide the steps for creating or configuring that skill, so this is best understood as a launch pattern for an existing skill.
The two launch methods serve different entry points. A quick step is available from the library interface, while a button on the site home page can start the same process without requiring the user to open the library first. The button works in the example because the skill already contains the library and process details.
Users should be able to access the SharePoint site and the data involved in the process. The example uses a compliance library, but the same idea is presented as a way to make a skill-based form easier to reach. Whether a particular tenant can use this pattern depends on the Copilot and skill capabilities configured in that environment.
The first route starts in the document library. Daniel Anderson [MVP] opens the library’s three-dot menu, chooses Integrate, and selects the quick step named Overdue Documents. That quick step runs the skill, which gathers documents for review and opens the interactive form.
The second route begins on the SharePoint home page. The user selects a button that invokes the same skill, which knows which library to inspect and which process to follow. The form then appears even though the user did not navigate to the library first.
Both routes lead to the same core sequence: the skill gathers information, the user makes decisions in the form, and Copilot asks before applying updates. In the example, the form includes a warning that marking one document expired would leave a subcontractor without an approved, in-date public liability certificate. That kind of contextual warning can help reviewers understand the consequence of a choice before submitting it.
A quick step is convenient when users are already working in the library, but it can be easy to overlook in the three-dot menu. The home-page button gives the process a more visible starting point and avoids the need to open the library first. Both methods still rely on the same skill; they are alternate ways to launch it, not separate form workflows.
The example should not be treated as a complete compliance configuration. It uses sample data, and the demonstrated form’s behavior depends on what the skill is set up to retrieve and do. Before using a similar process with real documents, confirm that the skill targets the intended library and that its actions and warnings fit the organization’s review process.
Keep the confirmation step in mind: submitting the form sends decisions to Copilot, but the user still has to approve the update. Review the proposed changes carefully before confirming. The demonstration establishes the launch and review flow, rather than detailing how to build skills, create the button, or configure the underlying process.
Open the library’s three-dot menu, choose Integrate, and select the quick step configured to run the relevant skill.
Yes. A home-page button can invoke a skill that already knows which library to check and which process to follow.
No. After submission, Copilot asks the user to confirm before applying the updates.