SharePoint site columns for consistent Copilot search

Key insights

• A site column is a reusable field that can be added to multiple SharePoint libraries.
• The demo uses a DocumentStatus choice column and a NextReviewDate date column.
• Putting a site column in a group makes it easier to find when adding it to a library.
• Consistent choice values let a search page filter documents across three libraries.
• Copilot asks for confirmation before applying the demonstrated metadata updates.

SharePoint site columns let you reuse the same metadata fields across document libraries, helping keep values consistent for filtering and cross-library search. This approach is useful to SharePoint site owners and people who organize or search documents across several libraries. Daniel Anderson [MVP] demonstrates the setup with two site columns, three libraries, and a Copilot-assisted search page.

What's new

The core feature is not new: a site column is a reusable column definition that can be added to multiple SharePoint lists or libraries. The practical point is that consistent metadata becomes more useful when people use Copilot to update documents or build reporting and search experiences from that information.

In the example, three document libraries—Site Reports, Compliance Documentation, and Permits and Approvals—need to track the same two attributes: document status and next review date. The site owner creates a choice column called DocumentStatus and a date-and-time column called NextReviewDate, then adds both fields to each library.

The status options are Draft, Submitted, Approved, and Expired. Because the same column definition and choice values are reused, the example avoids having one library use “New” where another uses “Draft” for the same meaning. That consistency supports common filters and a cross-library search page.

Who it is for and what you need

This method is for SharePoint site owners or library managers who need shared metadata across document libraries. The demonstrated setup requires a SharePoint site with the relevant libraries and permission to access site settings and change library settings.

The example uses Copilot in SharePoint to update document metadata and generate an HTML search page. The material does not identify a required license, specific plan, tenant configuration, region, or rollout stage, so those requirements cannot be confirmed here.

The demo uses sample documents and sample metadata. It does not establish that Copilot will produce the same page or updates in every environment, nor does it describe a general availability status for the Copilot capabilities shown.

How it works

Create each field once at the site level, then add it to the libraries that need it. In the demonstration, site columns are accessed through the site settings rather than created separately inside each library.

1. Open Site information, select View all site settings, and choose Site columns under Web Designer Galleries.
2. Create DocumentStatus as a Choice column. Enter the shared values Draft, Submitted, Approved, and Expired. The demo assigns it to a custom group called CopilotReady.
3. Create NextReviewDate as a Date and Time column. The demonstration leaves its other settings at their defaults and does not place it in the custom group.
4. For each document library, open Library settings, choose More library settings, and select Add from existing site columns. Add DocumentStatus from CopilotReady and NextReviewDate from Custom Columns.
5. After documents are present, Copilot can be prompted to set statuses and review dates. In the example, a human confirmation step appears before the proposed changes are applied.
6. With metadata populated, Copilot is prompted to create an HTML page that searches the three libraries. The requested page includes status checkboxes, document cards with file names and review dates, a search field, and a library filter.

The demonstrated page is published and reflects document changes: after files are deleted from one library, the displayed total changes. This illustrates the live relationship shown in the example, not a guarantee about every custom page or implementation.

Limitations and open questions

A site column standardizes the field definition, but teams still need to use the intended values and maintain the metadata. The demonstration shows Copilot setting the fields with user approval; it does not establish that the resulting values are authoritative or correct without review.

The page is a generated HTML experience, and the source does not explain its implementation, security model, permissions behavior, or how to maintain it. It also does not give a complete guide to troubleshooting Copilot output, assigning licenses, or deploying the approach across sites.

The example’s practical lesson is narrower and actionable: define shared columns and controlled choice values before building filters or reports that span multiple libraries. No official Microsoft documentation link was supplied with the source material, so availability and licensing details remain unverified.

Sources

• Daniel Anderson [MVP] demonstration of site columns and Copilot in SharePoint

Frequently asked questions

What is a SharePoint site column?

It is a reusable column definition that you can add to multiple SharePoint lists or document libraries.

How do I add a site column to a document library?

Open Library settings, select More library settings, then choose Add from existing site columns. Select the site column and add it to the library.

Do SharePoint site columns require a Copilot license?

The site-column setup does not state a license requirement. The demonstration uses Copilot, but the provided material does not specify the license or plan needed.

Why use the same choice values across document libraries?

Shared values help avoid inconsistent terms for the same status, supporting common filters and cross-library reporting or search.