Users with an OmniStudio license assigned but without the OmniStudio User permission set (API name: OmniStudioUser) will experience the following symptoms on any page that contains OmniStudio components:
runtime_omnistudio_common/toast or a similar assertion failureThe OmniStudio license authorizes access to the feature; the OmniStudio User permission set loads the OmniStudio runtime. Without the permission set, the runtime never initializes and the components cannot render or execute. System Administrators do not exhibit this behavior because they typically have the OmniStudio Admin permission set assigned by default, which includes runtime access.
This issue is distinct from users who have no OmniStudio license at all. A user may appear to have proper access (license shown as assigned) but still experience these symptoms if the permission set is absent.
There may be two permission sets with the label "OmniStudio User." Select the one whose API name is OmniStudioUser (not OmniStudio_User or similar). You can confirm the API name by clicking into the permission set detail page.
If users are managed through a Permission Set Group, add the OmniStudio User permission set to the relevant group instead of assigning it directly to individual users.
Note: The run-only OmniStudio User permission set is sufficient for users who need to view FlexCards and run OmniStudio-based actions. OmniStudio Admin is only required for users who build OmniStudio components.
Internal Information: Related case: 473776845. Issue presented in a Nonprofit Cloud org using Benefit Schedules and FlexCard-based Benefit record layouts. The OmniStudio Admin permission set was present on the System Administrator user but absent on non-admin program users. The license alone (OmniStudio listed in Permission Set Licenses) is not sufficient — the permission set is the gating control for runtime loading.
005387164

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.