In some cases, it may be necessary for project administrators or client services to lock a project to prevent content from being updated or changed for a period of time.

When a project is locked, Project Admins can't rename, move, copy, add files, or perform redactions. In short, no action can be taken that impacts or changes the project's document index. Functionality in other tabs like Settings, Permissions, Users, Analytics, and Q&A is still available in locked projects.
 
To lock a project:

  1   Select the Settings tab.

  2   Select Lock/Freeze Project.

  3   In the 'Lock Project Content' card, slide the toggle to the right.

Only full project admins or customer service can lock a project. If a project contains files in Action Required or still processing, these must be addressed before the project can be locked.

Project locks are typically short-term (a few minutes to an hour), after which the project can again be updated.

Reasons for locking a project include:

• Large project updates - If an administrative team requests large or complicated content updates or rearrangements, client services may lock the project while performing updates, eliminating the possibility of admin updates being made concurrently
• Archiving data or creating media - Media creation and data archiving require a static Index in order to extract an accurate compilation of site content
• Project closure - After a request from project administration to close a project, a project might be locked for a short period prior to deactivating users and processing the closure request