How do I put documents on legal hold?
Use FormKiQ's native legal-hold operation with the required governance permission, then verify that prohibited changes and deletion are blocked. In v1.19.2 the hold also blocks checkout. Record the matter reference and authorized release process. A custom hold label is not enforcement, and an application hold does not automatically configure immutable AWS storage or preserve every external copy.
Apply and verify the hold
Use the document action in FormKiQ Web or the documented PUT /documents/{documentId}/legalHold operation. Supply the correct site and the version-specific headers/request values from the legal-hold how-to. Keep the business reason and matter reference in the approved case record.
Test an ordinary user's edit, deletion, and checkout attempts on a held test document. Verify the native hold state instead of relying on a visual label or a governance attribute with a similar name.
Release through an authorized process
The corresponding DELETE operation removes a hold; it does not establish that destruction is permitted. Re-check retention, disposition eligibility, and the organization's legal authorization before resuming deletion.
Identify versions, artifacts, exports, backups, signed copies, and retrieval indexes within the preservation scope. FormKiQ governance checks and storage immutability are different controls. Define how the matter's preservation instructions apply across those locations and who records verification.
Edition and configuration
Legal hold requires the commercial governance implementation and appropriate GOVERN/ADMIN permissions. Follow the installed release contract; site/governance grants are different from folder permission entries.