---
schema_version: "1"
id: 1610bcc5dac50667905a144f7c276ef4ebe4d3a3057a6f0d9c89338625939efe
title: Troubleshoot Component Access in Omnistudio for Managed Packages
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_security_troubleshoot_comp_access.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_security_troubleshoot_comp_access.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7e1f33f844d82e8165ac9cf3c59307ddcb73602d10fa81d108e4569ff1c3c861
description: "Identify and resolve access-related issues in your orgs:"
products:
  - Omnistudio
release: "264"
---
# Troubleshoot Component Access in Omnistudio for Managed Packages

Identify and resolve access-related issues in your orgs:

1. In orgs without an Omnistudio license, follow these steps to verify the feature flag status for `AdvancedOmnistudioAccessCheck`, `ApexClassCheckForIP`, `ApexClassCheck`, `EnforceDMFLSAndDataEncryption`, and `EnableQueryWithFLS`:
    1. From Setup, in the Quick Find box, enter Custom Settings, and then select **Custom Settings**.
    2. Click **G** and go to **General Settings**.
    3. Verify whether the flag is set to true. If it’s false, these specific security checks are not active.
2. In orgs with an Omnistudio license, follow these steps to verify the feature flag status for `AdvancedOmnistudioAccessCheck`, `ApexClassCheckForIP`, `ApexClassCheck`, `EnforceDMFLSAndDataEncryption`, and `EnableQueryWithFLS`:
    1. From Setup, in the Quick Find box, enter Omni Interaction Configuration, and then select **Omni Interaction Configuration**.
    2. Verify whether the flag is set to true. If it’s false, these specific security checks are not active.
3. Verify the object-level access. Make sure that the user's profile or permission set has the necessary read, create, edit, or delete access for the object.
    1. From Setup, in the Quick Find box, enter Profiles, and then select **Profiles**.
    2. Click the user’s profile that you want to verify for the object-level access.
    3. Locate the user’s object in the **Custom Object Permissions** or **Standard Object Permissions** section, and verify whether the **Read**, **Create**, **Edit**, and **Delete** checkboxes are selected.
4. Verify field-level security (FLS). If specific fields are missing from dropdowns or picklists, verify FLS for the object.
    1. From Setup, in the Quick Find box, enter Profiles, and then select **Profiles**.
    2. Click the user’s profile that you want to verify for FLS.
    3. Locate the user’s object in the **Field-Level Security** section, and click **View**.
    4. Verify whether the **Read Access** and **Edit Access** (if applicable) checkboxes are selected.
5. Verify custom settings and make sure that the user profile has the specific custom setting definition assigned. For more information about custom settings, see [View and Edit Custom Settings](https://help.salesforce.com/s/articleView?id=platform.cs_detail.htm&language=en_US&type=5).
    1. From Setup, in the Quick Find box, enter Custom Settings, and then select **Custom Settings**.
    2. Click the name of the custom setting that you want to view.
6. Verify whether the View Setup and Configuration user permission is enabled. This permission is required for accessing named credentials and metadata. For more information about permissions, see [User Permissions](https://help.salesforce.com/s/articleView?id=platform.admin_userperms.htm&type=5&language=en_US).
    1. From Setup, in the Quick Find box, enter Profiles, and then select **Profiles**.
    2. Click the user's profile that you want to view.
    3. In the Profiles page, under the Administrative Permissions section, verify whether the **View Setup and Configuration** checkbox is selected.
7. Verify whether the user has permission to publish or subscribe to `VlocityTrackingEvent__e`.
    1. From Setup, in the Quick Find box, enter Permission Sets, and then select **Permission Sets**.
    2. Click the name of the permission set that you want to view.
    3. In the Permission Sets page, under the Apps section, click **Object Settings**.
    4. In Objects list, locate the `VlocityTrackingEvent__e` and verify whether the Read and Create permissions are assigned.
8. As a quick workaround, use one of these methods to resolve access issues:
    
    1. Grant the missing object, Field, or Custom Setting permissions through a Permission Set to the affected users.
    2. If an immediate fix is required when you audit permissions, you can leave the value of `AdvancedOmnistudioAccessCheck` or `ApexClassCheckForIP` as `false` in General Settings.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png)
    
    Note Use this only as a temporary workaround to maintain business continuity. After the necessary permission updates are complete, we recommend re-enabling it to make sure that your org remains aligned with the latest security access validations.