Learn how to update your Vault for enhanced security control for regions, blind protection, and organizations.

About the Feature

Case Access Group Security significantly simplifies security around access to Cases and unblinded information on Cases. 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-Study Products 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

When you complete configuration, Manage Case Access Group Security describes how to use this feature.

23R2 Update: Simplified Case Access Group Security Setup

In 23R2, setting up Case Access Groups is made even simpler. 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 the (23R2) enablement instructions to configure your Vault for the updated feature.

Overview of Enablement Steps

The following list is an outline of the procedures for enabling Case Access Group Security.

  1. Prerequisite: Contact Veeva Managed Services
  2. Configure and Update Layouts
  3. Turn Off Row-Level Security
  4. Turn On Case Access Group Security
  5. Update Object Lifecycle Roles and Atomic Security
  6. Update the Matching Sharing Rules on Document Lifecycles
  7. (Optional) Add and Configure Calculate Access Group User Actions
  8. (23R2) Configure Simplified Case Access Group Security Setup

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 the following:

  • Configuring Case Access Groups based on your business processes and use cases
    • This includes 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
    • This includes managing appropriate access to PII and unblinded information within set lifecycle states.

Configure and Update 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.
  • Marget 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
    • Section Name: access_group__c
  5. Insert the User Access Group Assignment related object.
    • Section Label: User Access Group Assignment
    • Section Name: user_access_group_assignment__c
  6. Insert a Detail Form section.
    • Section Label: System
    • Section Name: details1__c
    • 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. (Optional) To rearrange sections, drag and drop.
  9. Select Save.

Sample Case Access Group Layout

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 Name: details1__c
    • 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. (Optional) To rearrange sections, drag and drop.
  7. 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 Safety-EDC Vault Connection)
    • Study Type
    • Study
    • Market Segment
  4. Insert a Detail Form section.
    • Section Label: System
    • Section Name: details1__c
    • 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. (Optional) To rearrange sections, drag and drop.
  7. 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
    • Section Name: products__c
  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 Name: details1__c
    • 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. (Optional) To rearrange sections, drag and drop.
  10. Select Save.

Sample Market Segment Layout

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. In the Case Validity and Source section, 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. In the Details section, 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. In the Details section, 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:

  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. (Optional) To rearrange sections, drag and drop.
  5. Select Save.

Turn Off Row-Level Security

Turning off row-level security on Inbox Items and Cases includes removing all Sharing Rules and turning off Custom Sharing Rules and Matching Sharing Rules on all Inbox Item, Case, Localized Case, User, and Person objects. Use the following list to track your progress.

  • 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)
  • Person (person__sys)
  • Transmission (transmission__v)
  • Transmission Message (transmission_message__v)
  • User (user__sys)

Remove Sharing Rules

To remove Sharing Rules on an object, complete the following steps:

  1. Go to Admin > Configuration > Objects > [object] > Sharing Rules.
  2. Select the first Sharing Rule in the list.
  3. Select Delete.
  4. On the Deleting “[object]” dialog, select Continue.
  5. Repeat steps 2–4 until all of the Sharing Rules are deleted.

Turn Off Custom Sharing Rules and Matching Sharing Rules

To remove Custom Sharing Rules and Matching Sharing Rules on an object, complete the following steps:

  1. Go to Admin > Configuration > Objects > [object] > Details.
  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

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.

Sample Case Access Groups Settings

Update Object Lifecycle Roles and Atomic Security

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.

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

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 (Add) 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.

Sample Case Adverse Events Lifecycle Atomic Security Settings

Adjust Atomic Security for Blinded Information

Atomic Security for blinded information 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 information that should be blinded.

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

Updating Atomic Security for Blinded Information

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

  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 (Add) icon next to the Study Unmasked role.
  6. Select OK.
  7. For the applicable fields, configure the following Atomic Security settings:
    • Default: Hide
    • Study Unmasked: Edit
  8. Select Save.

Sample Case Assessment Expectedness Lifecycle Atomic Security Settings

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

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.

Sample AER - Data Entry Matching Sharing Rules Settings

(Optional) Add and Configure Calculate Access Group User Actions

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

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

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.

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.