# Manage Strict Case Locking

Learn how to enable and configure strict _Case_ locking in your Vault.

## About Strict Case Locking

Users can use strict _Case_ locking to prevent other users from editing the _Case_ and _Case_-descendent objects unless they are assigned to that _Case_ in the _Locked By_ field. This capability enforces restrictions on _Case_ editing permissions for organizations that require more security.

For more information, see <a href="/en/lr/01170/">Lock and Unlock a Case</a>.

## Prerequisites

To use this feature, you must <a href="/en/lr/01374/">enable Manual Case Locking: User Check In and Check Out</a>.

## Configure Strict Case Locking {#configure}

To manage strict _Case_ locking, navigate to **Admin > Settings > Safety Security Settings**.

Perform the following configurations in the _Case Locking_ section:
* To turn on the strict _Case_ locking capability, select the **Enable Strict Case Locking** checkbox.
* To specify certain _Case_ (`case_version__v`) fields that should remain editable to users even with strict _Case_ locking turned on, in the **Excepted Fields** drop-down, enter or select the desired fields. You cannot specify exceptions for _Case_-descendant objects.
<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: The <em>Receipt Date</em> and <em>New Info Date</em> fields appear twice in the drop-down. If you require these fields to be an exception to strict <em>Case</em> locking, select both corresponding fields that appear.</p>
    </div>
  </div>
</div>



## Objects Affected by Strict Case Locking {#objects-affected}

The following list outlines the objects that are protected by strict _Case_ locking:
* _Case_ (`case_version__v`)\
  This includes the _Case_ (`case__v`) and _Parent Information_ (`parental_case__v`) object types.
* _Case Adverse Event_ (`case_adverse_event__v`)
* _Case Assessment_ (`case_assessment__v`)
* _Case Assessment Expectedness_ (`case_assessment_expectedness__v`)
* _Case Assessment Result_ (`case_assessment_result__v`)
* _Case Cause of Death_ (`case_cause_of_death__v`)
* _Case Contact_ (`case_contact__v`)
* _Case Drug History_ (`case_drug_history__v`)
* _Case Diagnosis_ (`case_diagnosis__v`)
* _Case Identifier_ (`case_identifier__v`)
* _Case Medical History_ (`case_medical_history__v`)
* _Case Product_ (`case_product__v`)
* _Case Product Dosage_ (`case_product_dosage__v`)
* _Case Product Indication_ (`case_product_indication__v`)
* _Case Product Substance_ (`case_product_substance__v`)
* _Case Relationship_ (`case_relationship__v`)
* _Case Study Registration_ (`case_study_registration__v`)
* _Case Test Result_ (`case_test_result__v`)

## Actions Affected by Strict Case Locking {#actions-affected}
The following list outlines the actions that are protected by strict _Case_ locking:
* _Generate CIOMS I_
* _Generate E2B (R3)_
* _Generate FDA3500A_
* _Re-generate Domestic Case_
* _Re-render Case Narrative_
* _Void Case_

## User Actions That Lock Cases {#user-initiated-scenarios}
In Vaults with strict _Case_ locking enabled, Vault prevents conflicting _Case_ edits in the following user-initiated scenarios by locking the _Case_ to the initiating user and setting the _Locked By_ value to _System_:

* When a user navigates to the <a href="/en/lr/826980/">_Inbox Item to Case Compare_ page</a>
* When a user selects the <a href="/en/lr/01169/">_Generate Assessments_ action</a> on a _Case_
* When a user selects the <a href="/en/lr/01142/">_Promote to Multiple Cases_ action</a> on an _Inbox Item_

Once the action is complete, Vault unlocks the _Case_ and clears the _Locked By_ value.

[1]: #configure
[2]: #objects-affected
[3]: #actions-affected
[4]: #user-initiated-scenarios