MENU
A user attempts to launch an OmniScript from a record page, but an error message appears: "You do not have permission to access the Lightning Component [OmniScript Name]." The OmniStudio Developer confirms the user's profile has the Vlocity OmniScript runtime access enabled.
What is the most likely security-related cause the developer should investigate?
Runtime OmniScript access alone is not always enough when the OmniScript executes Data Mappers, Integration Procedures, or Remote Actions that rely on Apex-backed services. Salesforce has OmniStudio security checks for Apex class access, and its documentation specifically describes configuring Apex class permission checkers so users require explicit access to the Apex class that administers a Remote Action. Save Options do not control Lightning component authorization. Multi-language settings affect labels and translations, not runtime component permissions. FlexCard permissions are not the most likely cause because the error occurs while launching an OmniScript and the scenario already confirms OmniScript runtime access. The developer should therefore investigate missing Apex class access behind the OmniScript's actions.
================
Currently there are no comments in this discussion, be the first to comment!