Require key metadata
Define required SharePoint columns so documents cannot bypass essential project information.
Protect uses one standard JSON Schema to guide property entry and publish equivalent native SharePoint validation for document libraries.
Separate rules drift. Protect keeps the policy used to fill selected file properties aligned with the validation SharePoint applies on every edit. A preview explains how each rule will be enforced before anything is published.
Define required SharePoint columns so documents cannot bypass essential project information.
Use choices, formats, patterns, and related-column rules to improve metadata consistency.
Express file naming relationships from SharePoint column values in the same governed policy.
Preview native enforcement and stop unsupported rules instead of silently publishing an approximation.
Describe required properties, accepted values, formats, and naming relationships in standard JSON Schema.
Review how Protect maps each rule to SharePoint list or column validation.
Save the policy and its equivalent native validation only when the complete rule set is supported.
Use Fill properties for selected files while SharePoint continues enforcing the same policy on later edits.
Yes. Protect can publish supported required-field and value rules as native SharePoint validation for the document library.
Yes. The JSON Schema can relate SharePoint column values to a naming structure, subject to the supported native validation mapping shown in the preview.
Protect rejects unsupported rules instead of publishing a weaker approximation, so administrators can revise the policy deliberately.