OmniStudio and Vlocity Access FAQ

Proper access configuration is essential when working with OmniStudio/Vlocity components. Missing or incorrect permissions can cause components to fail to display or execute.

This article highlights the key areas to review to ensure users have the correct access and permissions.

1. Object Permissions:

When working with Vlocity orgs, it is important to review the data model, as sObject names may vary depending on the specific data model used.

Find the DataModel

1. Vlocity Packages
   • For Custom Data Model orgs: review Vlocity sObject access.
   • For Standard Data Model orgs: review OmniStudio sObject access.
2. OmniStudio Package
   • Review OmniStudio sObject access for the org.

For detailed descriptions of each object, refer to the following documents:

• Vlocity sObject Descriptions
• OmniStudio sObject Descriptions

To learn more about object permissions, see: Object Permissions

OmniStudio Permissions - OmniStudio Permission Sets

Note: Permissions are granted via Profiles, Permission Sets, and managed through Roles and Sharing Rules to control access levels for different users.

2. System Permissions:

Ensure that the appropriate system permissions are enabled in the user’s Permission Set:

• For internal users: Enables business users to execute OmniScripts, DRs, Cards, etc, in employee facing apps.
• For external users: Enables consumers and partners to execute OmniScripts, DRs, Cards through a Community or off platform.

3. Apex Class and Visualforce Page Access:

If functionality still does not work and the org has OmniStudio/Vlocity packages installed, verify the following:

Apex Class Access

• ComponentController
• BusinessProcessDisplayController
• NewportUtilities
• PlatformObjectMappings
• FlexCardController
• FlexRuntime
• FetchStaticResourceUrl

Visualforce Page Access

• OmniScriptInstancePage
• UserCustomLabels

Note: Access to other namespace classes or pages may be required depending on the implementation.