Tutorial · Microsoft 365 · Beginner

Design SharePoint document libraries for automation and Copilot

Columns, content types, folders vs metadata, and naming conventions that make flows and Copilot agents work well.

LevelBeginner
Time30 minutes
TopicMicrosoft 365

You'll need

  • SharePoint site owner

Metadata over deep folders

Use a few folders for permissions and lifecycle stages (To Sign, Signed, Archive) and columns for everything else (customer, type, status, dates). Flows filter by columns; Copilot uses titles and content.

Columns every document workflow needs

  1. Status (choice)
  2. Owner (person)
  3. Key date (date) — expiry, review, retention
  4. External reference (text) — agreement ID, PO number, e-Invoice UUID

Naming conventions

Readable names help both people and Copilot: 2026-10 Supplier Agreement - Syarikat Maju - signed.pdf. Avoid scan0001.pdf.

Permissions

Break inheritance only at library or top-folder level. Item-level permissions don't scale and confuse agents.

Tips

  • Turn on versioning with a sensible limit; flows that update metadata create versions too.