HowCurio SharePoint worked examples

These files are synthetic teaching material, not a tenant export or a completed SharePoint trial. They contain no real clients, account identifiers, or credentials.

Sensitivity example: General=1, Confidential=2, Restricted=3 is a fictional label hierarchy. Actual priority comes from the organization's configured label order. The local tool assumes file labeling is enabled, licensing and site-admin permissions are correct, and the chosen label uses a supported configuration. It does not check those assumptions or apply labels. CSV fields: Action is upload/web-edit/app-save/untouched; AppliedBy is none/manual/automatic/policy/unknown; HasContent is true/false.

Run with Node.js, after saving both files to the same local folder:
node label-coverage.mjs label-inputs.csv Confidential 2 true
Change your input rows or pass false to model PDF support being disabled. The modeled default-eligible Office extensions are docx, docm, xlsx, xlsm, xlsb, pptx, ppsx. MP4 is excluded; Microsoft documents manual video labeling, not default labeling. The tool does not model protected-upload access rights, policy propagation, Save As coauthoring delays, or every possible label configuration.

Metadata example: metadata-schema.json describes an imaginary Invoice/MeetingNotes/Document library. metadata-before.csv and metadata-after.csv illustrate incomplete rows and finished properties, with checkout released where illustrated. Empty columns can be valid when that content type does not require them. ProjectID 000742 is text; import that column as Text in a spreadsheet to preserve its leading zeroes. The CSV does not configure SharePoint, validate real tenants, or prove another user's access.

The example CSV values have no spreadsheet formula prefixes. When replacing them with exported or untrusted data, inspect values before opening a CSV in a spreadsheet. A label on a CSV does not make embedded formulas safe.