SharePoint Library Schema
Editable SharePoint library schema and approval matrix. Not a Microsoft template. Payment stays outside.
Download the SharePoint library schema
The SharePoint Library Schema and Approval Matrix is an editable workbook for one intake library. It is not a Microsoft template, not an e-sign kit, and not a payment control pack.
SharePoint holds the library, metadata, identity, versions, and the controlled record. Power Automate orchestrates. AI Builder or Azure Document Intelligence extracts.
What you get
- An editable workbook covering the layer boundary, decision record, content types, column dictionary, business Status and ModerationStatus, roles, views, naming and version rules, duplicate keys, Power Automate and IDP handoff maps, exception taxonomy, retention questions, seven fictional cases, rollout, and proof gates
- CSV companions for columns, statuses, roles, exceptions, and cases
- Seven Cedar & Quay library-control cases. They do not measure OCR
Anonymous approval is rejected. High-confidence extraction does not auto-release. Payment and supplier bank-detail changes stay outside. Retention labels are questions, not a compliance certificate.
How to start
- Open the workbook ReadMe sheet.
- Fill DecisionRecord.
- Walk Case01 through Case07.
- Read the paired guide: SharePoint Document Processing.
If the library purpose, named approvers, or the draft destination are still unclear, discuss the gaps on a fit call. If they are named, book a fit call to scope an AI Automation Systems build.
Map the library before connecting the workflow
Read the ZIP instructions and compare the proposed columns and content types with one real library. Identify the record that holds the document, the business status your team uses and the ownership of required fields. SharePoint moderation state and a custom business-status column serve different purposes; map them explicitly.
Use the fictional library-control cases to check naming, versions and duplicate keys before adding an extraction or approval step. A successful file upload does not establish that the right metadata, access or retention settings were applied.
Check a document through its full handoff
Follow one sample from intake into the library and through the agreed next action. Then try a revised file, an existing duplicate key and an item missing required metadata. Record where the exception appears and who resolves it.
Keep the library as the agreed system of record rather than allowing a parallel automation table to become an unexplained second version. This pack supplies a schema and control design; it does not configure your tenant or measure OCR accuracy. Use the document approval template when a person must authorise the next step, and test that decision against the document version actually reviewed.