# Enable Case Access Group Security

Case Access Group Security significantly simplifies security around access to _Cases_ and unblinded information on _Cases_ with enhanced security control for regions, blind protection, and organizations. With this feature, you have more granular control over _Case_-level access based on such factors as sponsor, report type, country, market segment, and more.

With Case Access Group Security enabled, you set limits for the following areas:

* Which _Cases_ are accessible to team members, along with the role they have on those _Cases_
* Which team members can see and edit sensitive fields on unblinded _Products_
* When to apply protection to certain open _Study_ and non-<em>Study Products</em> on blind-protected _Cases_
* Which _Case Product Drug Roles_, such as _Concomitant_, are exempt from blind protection
* Which _Study Product Roles_, such as _Standard of Care_, are exempt from blind protection

<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>: Case Access Group Security is an alternative to DAC on <em>Inbox Items</em> and <em>Cases</em>. Before configuring Case Access Group Security, DAC must be turned off.</p>
    </div>
  </div>
</div>



When you complete configuration, <a href="/en/gr/01182/">Manage Case Access Group Security</a> describes how to use this feature.

## 23R2 Update: Simplified Case Access Group Security Setup

With the 23R2 release, Safety simplifies the process of setting up _Case Access Groups_. Optimized matching logic and the addition of a _Country_ field on _User Access Group Assignment_ records make the setup more flexible and reduce the administrative burden of creating many _Case Access Group Assignment_ records. See [(23R2) Configure Simplified Case Access Group Security Setup][8] to configure your Vault for this feature.

<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 optimized matching logic considers blank values on <em>Case Access Group</em> records to mean <em>Any</em> when Vault matches <em>Inbox Items</em> and <em>Cases</em> to <em>Case Access Groups</em>. To take advantage of this update, you may need to update your <em>Case Access Group</em> assignment rules. We recommend consulting with Veeva Managed Services before making these updates.</p>
    </div>
  </div>
</div>



## Prerequisite

Before configuring Case Access Group Security in your Vault, contact Veeva Managed Services. Based on your organization's needs, our team will work with you to design the simplest and most effective security solution. 

At a high level, we will consult with you on:

* Configuring _Case Access Groups_ based on your business processes and use cases, including identifying how many groups are required and their settings
* Defining the rules for which _Cases_ are assigned to each group
* Identifying specific object- and field-level permissions that can be managed through Atomic Security for personally identifiable information (PII) and unblinded information
* Assigning individual team members to _Case Access Groups_ based on roles and localization, including managing appropriate access to PII and unblinded information within set lifecycle states

## Overview

To configure this feature in your Vault:

* [Configure object layouts][2]
* [Turn off row-level security][3]
* [Turn on Case Access Group Security][4]
* [Update object lifecycle roles and atomic security][5]
* [Update Matching Sharing Rules on document lifecycles][6]
* [(Optional) Configure Calculate Access Group user actions][7]
* [(23R2) Configure Simplified Case Access Group Security Setup][8]

## Configure Object Layouts {#layouts}

To manage Case Access Group Security, you must configure the following layouts:

* Case Access Group
* User Access Assignment
* Case Access Group Assignment
* Market Segment

In addition, you must update the following layouts:

* Inbox Item
* Case
* Localized Case
* User
* Product
* Study
* Case Number

The required layout update includes adding some or all of the following fields:

* **Access Group:** Displays the matching Case Access Group for Inbox Items.
* **Intake Format:** Displays the format the Inbox Item was created from, such as an E2B file.
* **Intake Method:** Displays the method of intake for the Inbox Item, such as email.
* **Market Segment:** Displays the market segment associated with the study for Study Cases or the primary Product for postmarket Cases.

The specific updates for each layout are described in the following sections.

### Configure the Case Access Group Layout

Complete the following steps to configure the **Case Access Group** layout:

1. Go to **Admin > Configuration > Objects > Case Access Group > Layouts**.
2. Select **Case Access Group Detail Page Layout**.
3. Configure the **Details** section with the following fields:
   * **Group Name**
   * **API Name**
4. Insert the **Case Access Group Assignment** related object.
    * **Section Label:** Case Assignment Rules
5. Insert the **User Access Group Assignment** related object.
    * **Section Label:** User Access Group Assignment
6. Insert a **Detail Form** section.
    * **Section Label:** System
    * **Section Layout:** Detail Form - Two Columns
7. Configure the **System** section with the following fields:
   * **Created By**
   * **Created Date**
   * **Last Modified By**
   * **Last Modified Date**
8. Select **Save**.

### Configure the User Access Group Assignment Layout

Complete the following steps to configure the **User Access Group Assignment** layout:

1. Go to **Admin > Configuration > Objects > User Access Group Assignment > Layouts**.
2. Select **User Access Group Assignment Detail Page Layout**.
3. Configure the **Details** section with the following fields:
   * **Access Group**
   * **User**
   * **Role**
   * **User Blinded**
   * **PII Access**
   * **Localization**
4. Insert a **Detail Form** section.
   * **Section Label:** System
   * **Section Layout:** Detail Form - Two Columns
5. Configure the **System** section with the following fields:
   * **Created By**
   * **Created Date**
   * **Last Modified By**
   * **Last Modified Date**
6. Select **Save**.

### Configure the Case Access Group Assignment Layout

Complete the following steps to configure the **Case Access Group Assignment** layout:

1. Go to **Admin > Configuration > Objects > Case Access Group Assignment > Layouts**.
2. Select **Case Access Group Assignment Detail Page Layout**.
3. Configure the **Details** section with the following fields:
   * **Access Group**
   * **Sponsor**
   * **Report Type**
   * **Country**
   * **Origin**
   * **Intake Format**
   * **Intake Method**
   * **Subject Information Review** (allows access to SAE subject data from the <a href="/en/gr/679350/">Safety-EDC Connection</a>)
   * **Study Type**
   * **Study**
   * **Market Segment**
4. Insert a **Detail Form** section.
   * **Section Label:** System
   * **Section Layout:** Detail Form - Two Columns
5. Configure the **System** section with the following fields:
   * **Created By**
   * **Created Date**
   * **Last Modified By**
   * **Last Modified Date**
6. Select **Save**.

### Configure the Market Segment Layout

Complete the following steps to configure the **Market Segment** layout:

1. Go to **Admin > Configuration > Objects > Market Segment > Layouts**.
2. Select **Market Segment Detail Page Layout**.
3. Configure the **Details** section to include the **Name** field.
4. Insert a **Product** related object section.
    * **Section Label:** Product
5. In the **Product** section, select **Edit Columns** to configure the columns in the following order:
    * **Product Name**
    * **Product Type**
    * **Organization**
    * **Abbreviation**
6. In the **Study** section, select **Edit Columns** to configure the columns in the following order:
    * **Study Number**
    * **Study Name**
    * **Protocol Title**
    * **Masking**
7. Insert a **Detail Form** section.
   * **Section Label:** System
   * **Section Layout:** Detail Form - Two Columns
8. Configure the **System** section with the following fields:
   * **Created By**
   * **Created Date**
   * **Last Modified By**
   * **Last Modified Date**
9.  Select **Save**.

### Update the Inbox Item Layout

Complete the following steps to update the **Inbox Item** layout:

1. Go to **Admin > Configuration > Objects > Inbox Item > Layouts**.
2. Select **Inbox Item Detail Page Layout**.
3. Add the following fields:
    * **Access Group**
    * **Intake Format**
    * **Intake Method**
    * **Market Segment**
4. Select **Save**.

### Update the Case Layout

Complete the following steps to update the **Case** layout:

1. Go to **Admin > Configuration > Objects > Case > Layouts**.
2. Select **Case Page Layout**.
3. Add the following fields:
    * **Access Group**
    * **Intake Format**
    * **Intake Method**
    * **Market Segment**
4. Select **Save**.

### Update the Localized Case Layout

Complete the following steps to update the **Localized Case** layout:

1. Go to **Admin > Configuration > Objects > Localized Case > Layouts**.
2. Select **Localized Case Detail Page Layout**.
3. Add the **Access Group** field.
4. Select **Save**.

### Update the Case Number Layout

Complete the following steps to update the **Case Number** layout:

1. Go to **Admin > Configuration > Objects > Case Number > Layouts**.
2. Select **Case Number Detail Page Layout**.
3. In the **Details** section, add the **Access Group** field.
4. Select **Save**.

### Update the Product Layouts

Complete the following steps to update Product layouts:

<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>: This change must be applied to all Product layouts.</p>
    </div>
  </div>
</div>



1. Go to **Admin > Configuration > Objects > Product > Layouts**.
2. Select a layout.
3. In the **Details** section, add the **Market Segment** field.
4. Select **Save**.

### Update the Study Layout

Complete the following steps to update the **Study** layout:

1. Go to **Admin > Configuration > Objects > Study > Layouts**.
2. Select **Study Detail Page Layout**.
3. In the **Details** section, add the **Market Segment** field.
4. Select **Save**.

### Update the User Layout

For a convenient way to assign individuals to Case Access Groups, insert the **User Access Group Assignment** section on the **User** layout.

1. Go to **Admin > Configuration > Objects > User > Layouts**.
2. Select **User Detail Page Layout**.
3. Insert the **User Access Group Assignment** related object section.
4. Select **Save**.

## Turn Off Row-Level Security {#row-level-security}

To turn off row-level security on _Inbox Items_ and _Cases_, [delete all Sharing Rules][9] then [turn off Sharing Rules][10] for the following objects:

* _Case_ (`case_version__v`)
* _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 Diagnosis_ (`case_diagnosis__v`)
* _Case Drug History_ (`case_drug_history__v`)
* _Case Drug History Substance_ (`case_drug_history_substance__v`)
* _Case Identifier_ (`case_identifier__v`)
* _Case Medical History_ (`case_medical_history__v`)
* _Case Number_ (`case_number__v`)
* _Case Product_ (`case_product__v`)
* _Case Product Device Code_ (`case_product_device_code__v`)
* _Case Product Dosage_ (`case_product_dosage__v`)
* _Case Product Indication_ (`case_product_indication__v`)
* _Case Product Registration_ (`case_product_registration__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`)
* _Inbox Item_ (`inbox_item__v`)
* _Localized Case_ (`localized_case__v`)
* _Localized Case Adverse Event_ (`localized_case_adverse_event__v`)
* _Localized Case Assessment_ (`localized_case_assessment__v`)
* _Localized Case Assessment Result_ (`localized_case_assessment_result__v`)
* _Localized Case Cause of Death_ (`localized_case_cause_of_death__v`)
* _Localized Case Comment_ (`localized_case_comment__v`)
* _Localized Case Contact_ (`localized_case_contact__v`)
* _Localized Case Document_ (`localized_case_document__v`)
* _Localized Case Drug History_ (`localized_case_drug_history__v`)
* _Localized Case Identifier_ (`localized_case_identifier__v`)
* _Localized Case Medical History_ (`localized_case_medical_history__v`)
* _Localized Case Product_ (`localized_case_product__v`)
* _Localized Case Product Device Code_ (`localized_case_product_device_code__v`)
* _Localized Case Product Dosage_ (`localized_case_product_dosage__v`)
* _Localized Case Product Indication_ (`localized_case_product_indication__v`)
* _Localized Case Product Substance_ (`localized_case_product_substance__v`)
* _Localized Case Test Result_ (`localized_case_test_result__v`)
* _Localized Case Translation_ (`localized_case_translation__v`)
* _Organization_ (`organization__v`)
* _Person_ (`person__sys`)
* _Product_ (`product__v`)
* _Study_ (`study__v`)
* _Study Arm_ (`study_arm__v`)
* _Study Indication_ (`study_indication__v`)
* _Study Product_ (`study_product__v`)
* _Study Product Group_ (`study_product_group__v`)
* _Study Product Placeholder_ (`study_product_placeholder__v`)
* _Study Registration_ (`study_registration__v`)
* _Study Site_ (`study_site__v`)
* _Transmission_ (`transmission__v`)
* _Transmission Message_ (`transmission_message__v`)
* _User_ (`user__sys`)
* _Validation Result_ (`validation_result__v`)

### Delete Sharing Rules {#delete-sharing-rules}

To delete Sharing Rules on an object:

1. Navigate to **Admin > Configuration > Objects > [Object] > Sharing Rules**.
2. Select the first Sharing Rule.
3. Select **Delete**.
4. In the _Deleting [Object]_ dialog, select **Continue**.
5. Repeat steps until all of the Sharing Rules are deleted.

 <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>: When all Sharing Rules have been deleted for an object, <a href="/en/gr/01304/#turn-off-sharing-rules">turn off its Custom Sharing Rules and Matching Sharing Rules</a> before moving on to delete the Sharing Rules of the next object.</p>
    </div>
  </div>
</div>



### Turn Off Sharing Rules {#turn-off-sharing-rules}

 <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>: You must first <a href="/en/gr/01304/#delete-sharing-rules">delete every Sharing Rule for an object</a> before you can turn off its Custom Sharing Rules and Matching Sharing Rules.</p>
    </div>
  </div>
</div>



To turn off Custom Sharing Rules and Matching Sharing Rules for an object:

1. Navigate to **Admin > Configuration > Objects > [Object]**.
2. Select **Edit**.
3. In the _Options_ section, clear the **Enable Custom Sharing Rules** and **Enable Matching Sharing Rules** checkboxes.
4. Select **Save**.

## Turn On Case Access Group Security {#cag-security}

Complete the following steps to turn on the Case Access Group Security feature in your Vault:

1. Go to **Admin > Settings > Safety Security Settings**.
2. Select **Edit**.
3. In the **Case Access Groups** section, select the **Enable Case Access Groups** checkbox.
4. (Optional) To limit the visibility of Vault users to each other by Case Access Group, select the **Secure Users by Case Access Group** checkbox. We recommend enabling this option in Contract Research Organization (CRO) Vaults. This ensures users can see only other users in the same Case Access Group. When not enabled, users can see all other users in the same Vault.
5. (Optional) In the **Blind-Protected Objects** field, select additional blind-protected objects.
    * By default, Case Product, Case Product Registration, and Case Product Substance are selected and cannot be removed.
6. (Optional) In the **Unprotected Drug Roles** field, select drug roles that do not require information to be blind-protected.
7. (Optional) In the **Unprotected Study Product Roles** field, select roles that do not require information to be blind-protected.
8. Select **Save**.

## Update Object Lifecycle Roles and Atomic Security {#lifecycle-atomic}

For all applicable Case and Case child object lifecycles, you must grant no permissions to the following roles:

* PII Unmasked
* Study Unmasked

In addition, you must configure the Atomic Security for PII and Blinded information.

### Grant No Permissions

To grant no permissions to a role for an object lifecycle, complete the following steps:

1. Go to **Admin > Configuration > Object Lifecycles > [object lifecycle]**.
2. In the **Roles** section, select **Edit**.
3. For the PII Unmasked and Study Unmasked roles, clear all checkboxes for all states to grant no permissions.
4. Select **Save**.


### Update Atomic Security for PII

Atomic Security for PII must be set for every state in the lifecycle for every field that includes sensitive information. Our recommended set of fields is outlined in the following list, but you should apply the changes to all fields that fall under your organization's definition of PII.

<table>
    <thead>
            <tr>
                <th>Object Lifecycle</th>
                <th>Field</th>
            </tr>
        </thead>
    <tbody>
            <tr>
                    <td>Case Lifecycle <br>
                        (<code>case_processing_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Age</li>
                            <li>Age (normalized)</li>
                            <li>Age (unit)</li>
                            <li>Age at Onset (Status)</li>
                            <li>Age At Vaccination (normalized)</li>
                            <li>Age at Vaccination (number)</li>
                            <li>Age at Vaccination (Status)</li>
                            <li>Age At Vaccination (unit)</li>
                            <li>Date of Birth</li>
                            <li>Date of Birth (normalized)</li>
                            <li>Date of Birth (reason omitted)</li>
                            <li>Date of Death</li>
                            <li>Date of Death (normalized)</li>
                            <li>Date of Death (reason omitted)</li>
                            <li>Delivery Method</li>
                            <li>Ethnicity</li>
                            <li>Ethnicity (Reason Omitted)</li>
                            <li>Event Onset</li>
                            <li>Event Onset (normalized)</li>
                            <li>Event Onset (reason omitted)</li>
                            <li>Sex</li>
                            <li>Gender (reason omitted)</li>
                            <li>Gestation</li>
                            <li>Gestation (unit)</li>
                            <li>Gravida/Gravidity</li>
                            <li>Height</li>
                            <li>Height (normalized)</li>
                            <li>Height (unit)</li>
                            <li>Last Menstrual</li>
                            <li>Last Menstrual (normalized)</li>
                            <li>Last Menstrual (reason omitted)</li>
                            <li>Medical History Text</li>
                            <li>Medical History Text (reason omitted)</li>
                            <li>Military Status</li>
                            <li>MRN - GP</li>
                            <li>MRN - GP (reason omitted)</li>
                            <li>MRN - Hospital</li>
                            <li>MRN - Hospital (reason omitted)</li>
                            <li>MRN - Investigation</li>
                            <li>MRN - Investigation (reason omitted)</li>
                            <li>MRN - Specialist</li>
                            <li>MRN - Specialist (reason omitted)</li>
                            <li>Number of Fetuses</li>
                            <li>Para/Parity</li>
                            <li>Patient First Name</li>
                            <li>Patient First Name (Reason Omitted)</li>
                            <li>Patient Initials</li>
                            <li>Patient Initials (reason omitted)</li>
                            <li>Patient Last Name</li>
                            <li>Patient Last Name (Reason Omitted)</li>
                            <li>Patient Middle Name</li>
                            <li>Patient Middle Name (Reason Omitted)</li>
                            <li>Pregnancy Conception Date</li>
                            <li>Pregnancy Due Date</li>
                            <li>Race</li>
                            <li>Race (Reason Omitted)</li>
                            <li>Reporter Country</li>
                            <li>Reporter Email Address</li>
                            <li>Reporter First Name</li>
                            <li>Reporter Last Name</li>
                            <li>Weight</li>
                            <li>Weight (normalized)</li>
                            <li>Weight (unit)</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Case Adverse Event Lifecycle <br>
                        (<code>case_adverse_event_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Cessation</li>
                            <li>Cessation (normalized)</li>
                            <li>Cessation (reason omitted)</li>
                            <li>Diagnosis</li>
                            <li>Event Country</li>
                            <li>Onset</li>
                            <li>Onset (normalized)</li>
                            <li>Onset (reason omitted)</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Case Cause of Death Lifecycle <br>
                        (<code>case_cause_of_death_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Cause of Death - MedDRA Coding Method</li>
                            <li>Cause of Death (LLT)</li>
                            <li>Cause of Death (PT)</li>
                            <li>Cause of Death (Reported)</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Case Contact Lifecycle <br>
                        (<code>case_contact_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>City</li>
                            <li>City Reason Omitted</li>
                            <li>Country</li>
                            <li>Country Reason Omitted</li>
                            <li>County</li>
                            <li>County (Reason Omitted)</li>
                            <li>Email Address</li>
                            <li>Email Address (Reason Omitted)</li>
                            <li>Fax</li>
                            <li>Fax (Reason Omitted)</li>
                            <li>First Name</li>
                            <li>First Name Reason Omitted</li>
                            <li>Middle Name</li>
                            <li>Middle Name Reason Omitted</li>
                            <li>Last Name</li>
                            <li>Last Name Reason Omitted</li>
                            <li>Postal Code</li>
                            <li>Postal Code Reason Omitted</li>
                            <li>State / Province</li>
                            <li>State / Province Reason Omitted</li>
                            <li>Street</li>
                            <li>Street Line 2</li>
                            <li>Street Line 2 (Reason Omitted)</li>
                            <li>Street Reason Omitted</li>
                            <li>Telephone</li>
                            <li>Telephone Reason Omitted</li>
                            <li>Title</li>
                            <li>Title Reason Omitted</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Case Diagnosis Lifecycle <br>
                        (<code>case_diagnosis_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Name</li>
                            <li>Name (MedDRA)</li>
                            <li>Name (MedDRA) - MedDRA Coding Method</li>
                            <li>Name (Reported)</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Case Drug History Lifecycle <br>
                        (<code>case_drug_history_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Age At Vaccination (normalized)</li>
                            <li>Age At Vaccination (number)</li>
                            <li>Age At Vaccination (Status)</li>
                            <li>Age at Vaccination (unit)</li>
                            <li>Indication (LLT)</li>
                            <li>Indication (LLT) - MedDRA Coding Method</li>
                            <li>Indication (PT)</li>
                            <li>Indication (Reported)</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Case Medical History Lifecycle <br>
                        (<code>case_medical_history_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Condition / Procedure (LLT)</li>
                            <li>Condition / Procedure (PT)</li>
                            <li>Condition / Procedure (Reported)</li>
                            <li>Continuing</li>
                            <li>Continuing Reason Omitted</li>
                            <li>End Date</li>
                            <li>End Date Normalized</li>
                            <li>End Date Reason Omitted</li>
                            <li>Family History</li>
                            <li>Name</li>
                            <li>Name (LLT) - MedDRA Coding Method</li>
                            <li>Start Date</li>
                            <li>Start Date Normalized</li>
                            <li>Start Date Reason Omitted</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Case Product Lifecycle <br>
                        (<code>case_product_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Age (normalized)</li>
                            <li>Date Explanted</li>
                            <li>Date Implanted</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Case Product Dosage Lifecycle <br>
                        (<code>case_product_dosage_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Dose (number)</li>
                            <li>Dose (unit text)</li>
                            <li>Dose (unit)</li>
                            <li>Dose Form</li>
                            <li>Dose Form TermID</li>
                            <li>Dose Form TermID Version</li>
                            <li>Dose Form Text</li>
                            <li>Dose Form Text (reason omitted)</li>
                            <li>Dose Number in Series</li>
                            <li>Dose Text</li>
                            <li>Dose Text (Long Text)</li>
                            <li>Duration (number)</li>
                            <li>Duration (Status)</li>
                            <li>Duration (unit)</li>
                            <li>First Administration</li>
                            <li>First Administration (normalized)</li>
                            <li>First Administration (reason omitted)</li>
                            <li>Frequency (number)</li>
                            <li>Frequency (unit)</li>
                            <li>Last Administration</li>
                            <li>Last Administration (normalized)</li>
                            <li>Last Administration (reason omitted)</li>
                            <li>Parent RoA</li>
                            <li>Parent RoA TermID</li>
                            <li>Parent RoA TermID Version</li>
                            <li>Parent RoA Text</li>
                            <li>Parent RoA Text (reason omitted)</li>
                            <li>Patient RoA</li>
                            <li>Patient RoA TermID</li>
                            <li>Patient RoA TermID Version</li>
                            <li>Patient RoA Text</li>
                            <li>Patient RoA Text (reason omitted)</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Case Product Indication Lifecycle <br>
                        (<code>case_product_indication_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Name</li>
                            <li>Name (MedDRA)</li>
                            <li>Name (MedDRA) - MedDRA Coding Method</li>
                            <li>Name (Reported)</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Case Test Result Lifecycle <br>
                        (<code>case_test_result_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Date</li>
                            <li>Date Normalized</li>
                            <li>Date Reason Omitted</li>
                            <li>Result</li>
                            <li>Result (Code)</li>
                            <li>Result (qualifier)</li>
                            <li>Result (Text)</li>
                            <li>Result (Unit)</li>
                            <li>Result (Unit) Text</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Localized Case Lifecycle <br>
                        (<code>localized_case_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Additional Pregnancy Related Information</li>
                            <li>Medical History Text</li>
                            <li>Reporter Country</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Localized Case Contact Lifecycle <br>
                        (<code>localized_case_contact_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Contact Country</li>
                            <li>First Name</li>
                            <li>Middle Name</li>
                            <li>Last Name</li>
                            <li>NMPA Patient Nationality</li>
                            <li>NMPA Patient Race</li>
                            <li>State / Province</li>
                            <li>Street</li>
                            <li>Street Line 2</li>
                            <li>Title</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Localized Case Cause of Death Lifecycle <br>
                        (<code>localized_case_cause_of_death_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Case Cause of Death</li>
                            <li>Cause of Death (Reported)</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Localized Case Medical History Lifecycle <br>
                        (<code>localized_case_medical_history_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Condition / Procedure (Reported)</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Localized Case Product Indication <br>
                        (<code>localized_case_product_indication__v</code>)</td>
                    <td>
                        <ul>
                            <li>Name</li>
                            <li>Name (Reported)</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Localized Case Test Result Lifecycle <br>
                        (<code>localized_case_test_result_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Result (Text)</li>
                        </ul>
                    </td>
        </tr>
    </tbody>
</table>

#### Updating Atomic Security for PII

For each state of the object lifecycle, complete the following steps to update Atomic Security for PII:

1. Go to **Admin > Configuration > Object Lifecycles > [object lifecycle]**.
2. In the **States** section, select a state.
3. In the **Atomic Security: Fields** section, select **Edit**.
4. On the **Atomic Security: Fields** page, select **Role Override**.
5. Select the **Plus** (<img class="inline" src="https://platform.veevavault.help/assets/images/saf-add-button.png" alt="Add" style="" />) icon next to the PII Unmasked role.
6. Select **OK**.
7. For the applicable fields, configure the following Atomic Security settings:
    * **Default:** Hide
    * **PII Unmasked:** Edit
8. Select **Save**.

### Configure Atomic Security on Fields for Blinded Information

<a href="/en/gr/47850/#how-to-set-atomic-security-on-fields">Set Atomic Security on fields</a>, including [_Role Overrides_][11], for every field that includes blinded (sensitive) information. We recommend setting Atomic Security on the specified fields in every state of the following lifecycles, but you should apply the changes to all fields that fall under your organization's definition of information that should be blinded.

<table>
            <thead>
                <tr>
                    <th>Object Lifecycle</th>
                    <th>Field</th>
                </tr>
            </thead>
            <tbody>
                <tr>
                    <td>Case Assessment Lifecycle <br>
                        (<code>case_assessment_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Expected</li>
                            <li>Expected (Status)</li>
                            <li>Listedness (Core)</li>
                            <li>Listedness (status)</li>
                            <li>Reaction Recurrence</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Case Assessment Expectedness Lifecycle <br>
                        (<code>case_assessment_expectedness_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Expected</li>
                            <li>Expected (Status)</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Case Assessment Result Lifecycle <br>
                        (<code>case_assessment_result_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Causality Established</li>
                            <li>Result</li>
                            <li>Result (Reported)</li>
                            <li>Result (Text)</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Case Product Lifecycle <br>
                        (<code>case_product_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Combination product</li>
                            <li>Combination Product Registration</li>
                            <li>Lot Number</li>
                            <li>Model Number</li>
                            <li>MPID</li>
                            <li>MPID Version</li>
                            <li>Product</li>
                            <li>Product (Coded)</li>
                            <li>Product (Reported)</li>
                            <li>Product (Study)</li>
                            <li>Product Code</li>
                            <li>Product Registration</li>
                            <li>Serial Number</li>
                            <li>Study Arm Product</li>
                            <li>Substances</li>
                            <li>Trade Name</li>
                            <li>Unique Identifier</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Case Product Dosage Lifecycle <br>
                        (<code>case_product_dosage_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Batch / Lot Number</li>
                            <li>Batch / Lot Number (reason omitted)</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Case Product Substance Lifecycle <br>
                        (<code>case_product_substance_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Substance Name</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Localized Case Product Lifecycle <br>
                        (<code>localized_case_product_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>CLocal MPID</li>
                            <li>Product (Reported)</li>
                            <li>Product (Coded)</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Localized Case Assessment Lifecycle <br>
                        (<code>localized_case_assessment_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Expected</li>
                            <li>Expected (Status)</li>
                        </ul>
                    </td>
                </tr>
                <tr>
                    <td>Localized Case Product Substance Lifecycle <br>
                        (<code>localized_case_product_substance_lifecycle__v</code>)</td>
                    <td>
                        <ul>
                            <li>Local Product Code</li>
                            <li>Substance Name</li>
                        </ul>
                    </td>
                </tr>
            </tbody>
        </table>

#### Add Role Overrides for Blinded Information {#role-overrides-blinded}

For the initial state of each applicable object lifecycle, <a href="/en/gr/47850/#how-to-set-atomic-security-on-fields">add a _Role Override_</a> for the _Owner_ role, then configure _Edit_ permissions for all applicable fields.

For each additional state of each applicable object lifecycle, <a href="/en/gr/47850/#how-to-set-atomic-security-on-fields">add a _Role Override_</a> for the _Study Unmasked_ role. For the applicable fields, configure the following role settings:

* **Default:** Select **Hide**
* **Study Unmasked:** Select **Edit**

### Update the User Role Setup Object

Complete the following steps to add the **Case Access Group** field to the **User Role Setup** object:

1. Go to **Admin > Configuration > Objects > User Role Setup > Fields**.
2. Select **Create**.
3. In the **Step 1: Select the field type** section, select **Object**.
4. In the **Step 2: Choose label and name for the field** section, in the **Label** field, enter "Case Access Group".
5. In the **Step 3: Set the options** section, complete the following steps:
   * In the **Object** picklist, select **Case Access Group**.
   * Select the **Display in default lists and hovercards** checkbox.
6. Select **Save**.

## Update the Matching Sharing Rules on Document Lifecycles {#sharing}

You must update the Matching Sharing Rules on all standard and custom roles for the following document lifecycles:

* AER Lifecycle
* Case Generated Document Lifecycle
* Case Source Lifecycle
* Narrative Lifecycle

1. Go to **Admin > Configuration > Document Lifecycles > [document lifecycle] > Roles**.
2. Select a custom role.
3. On the **Sharing Rules** tab, select a role.
4. Select **Edit**.
5. In the **Rule Criteria** section, complete the following steps:
    * Clear the **Organization (organization__v)** checkbox.
    * Select the **Case Access Group (case_access_group__v)** checkbox.
6. Select **Save**.

## (Optional) Add and Configure Calculate Access Group User Actions {#optional}

When Case Access Group details are edited, the Access Group assignments on existing Inbox Items and Cases may need to be updated. The update can be triggered through the **Calculate Inbox Item Access Group** and **Calculate Case Access Group** actions. Adding these actions impacts the following objects and object lifecycles:

* Inbox Item
* Inbox Item Lifecycle
* Case
* Case Lifecycle

<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 recalculation requires significant system resources. If you configure this action, we recommend that it is used only when there’s a major change to Case Access Group configuration. Case Access Group assignments are always calculated by the system when the Inbox Item is created and when the Case is promoted.</p>
    </div>
  </div>
</div>



### Add the Calculate Inbox Item Access Group Action to Inbox Items

To add the **Calculate Inbox Item Access Group** action to the **Inbox Item** object, complete the following steps:

1. Go to **Admin > Configuration > Objects > Inbox Item > Actions**.
2. Select **Create**.
3. In the **Create Action** window, select **Calculate Inbox Item Access Group** from the picklist and then select **Continue**.
4. (Optional) On the **Create Action** page, in the **Description** field, enter "Evaluate the assigned Case Access Group and update the Inbox Item if needed."
5. Select **Save**.

### Add the Calculate Inbox Item Access Group Action to the Inbox Item Lifecycle

To add the **Calculate Inbox Item Access Group** action to the **Inbox Item** object lifecycle, complete the following steps:

1. Go to **Admin > Configuration > Object Lifecycles > Inbox Item Lifecycle**.
2. In the **States** section, select a state. We recommend adding the action to the New and Active states.
3. In the **User Actions** section, select **Edit**.
4. Add an action with the following setup:
   * Always
   * Calculate Inbox Item Access Group
   * **Action Label:** Calculate Inbox Item Access Group
5. Select **Save**.

### Add the Calculate Case Access Group Action to Cases

To add the **Calculate Case Access Group** action to the **Case** object, complete the following steps:

1. Go to **Admin > Configuration > Objects > Case > Actions**.
2. Select **Create**.
3. In the **Create Action** window, select **Calculate Case Access Group** from the picklist and then select **Continue**.
4. (Optional) On the **Create Action** page, in the **Description** field, enter "Evaluate the assigned Case Access Group and update the Case if needed."
5. Select **Save**.

### Add the Calculate Case Access Group Action to the Case Object Lifecycle

To add the **Calculate Case Access Group** action to the **Case** object lifecycle, complete the following steps:

1. Go to **Admin > Configuration > Object Lifecycles > Case Lifecycle**.
2. In the **States** section, select a state. We recommend adding the action to the Triage and Data Entry states.
3. In the **User Actions** section, select **Edit**.
4. Add an action with the following setup:
   * Always
   * Calculate Case Access Group
   * **Action Label:** Calculate Case Access Group
5. Select **Save**.

## (23R2) Configure Simplified Case Access Group Security Setup {#r232}

The following section describes how to configure your Vault for assigning users to Case Access Groups based on country.

In addition, if you have configured your Vault to display **Transmission** records, you can include the Case Access Group and Case Access Group Assignment Reason on the **Inbound Transmission** record.

Finally, you can set up **User** records with the **Case Access Group Override** field. When populated with a Case Access Group, the system assigns all Inbox Items and Cases created by that user to that Case Access Group instead of running the matching logic. This is useful, for example, for a global load balancing Case Processor who may enter a Case that would qualify for a specific group though it should be maintained at the global level.

<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>: Before performing the following steps, you must complete all of the configuration listed above this section.</p>
    </div>
  </div>
</div>



### Update the User Access Group Assignment Layout

Complete the following steps to add the **Country** field to **User Access Group Assignment** records.

1. Go to **Admin > Configuration > Objects > User Access Group Assignment > Layouts**.
2. Select **User Access Group Assignment Detail Page Layout**.
3. In the **Details** section, add the **Country** field.
4. Select **Save**.

### Update the Inbound Transmission Layout

Complete the following steps to add the **Case Access Group** and **Case Access Group Assignment Reason** fields to **Inbound Transmission** records.

1. Go to **Admin > Configuration > Objects > Transmission > Layouts**.
2. Select **Inbound Transmission Detail Page Layout**.
3. In the **System** section, add the following fields:
    * **Case Access Group**
    * **Case Access Group Assignment Reason**
4. Select **Save**.

### Update the User Layout

Complete the following steps to add the **Case Access Group Override** field to **User** records.

1. Go to **Admin > Configuration > Objects > User > Layouts**.
2. Select **User Detail Page Layout**.
3. In the section of your choosing, add the **Case Access Group Override** field.
4. Select **Save**.

[2]: #layouts
[3]: #row-level-security
[4]: #cag-security
[5]: #lifecycle-atomic
[6]: #sharing
[7]: #optional
[8]: #r232
[9]: #delete-sharing-rules
[10]: #turn-off-sharing-rules
[11]: #role-overrides-blinded