Loading

Salesforce OmniStudio: "This feature is not currently enabled for this user" in Experience Cloud quote and course-registration flows after enabling OmniStudio

Julkaisupäivä: Jul 15, 2026
Kuvaus

This article covers the scenario where enabling the OmniStudio feature flag causes OmniStudio-driven components (FlexCards, OmniScripts, Integration Procedures) inside an Experience Cloud site to fail for community/portal users while the same components work for internal admins.

Customer Symptoms / Impact:

  • "Error in the intermediary community that prevents the product quote process due to the activation of the OmniStudio flag"

  • In browser developer tools, a server action to /s/sfsites/aura returns: "error": { "message": "This feature is not currently enabled for this user.", "statusCode": 403, "errorCode": "INSUFFICIENT_ACCESS" }

Trigger Conditions & Technical Context:

  • The OmniStudio feature is activated in Setup, but the affected community profile or permission set lacks the OmniStudio permission set assignment, Apex class access, or object/field-level access required by the OmniStudio runtime.

  • Affected users are external Experience Cloud users (for example, a portal login used for a course-registration or product-quote process); internal profiles with the OmniStudio permission set are unaffected.

Ratkaisu

Follow these steps to restore OmniStudio component access for Experience Cloud users after enabling the OmniStudio feature.

Cause 1: The community profile is missing the OmniStudio permission set.

  1. Go to Setup > Users > Permission Sets.

  2. Open the OmniStudio permission set that grants runtime access.

    • For OmniStudio-managed metadata, this is OmniStudioRuntime.

    • For package-based orgs, this is the vlocity_namespace runtime permission set.

  3. Click Manage Assignments > Add Assignment.

  4. Select every external/community user (for example, the portal or course-registration login) that runs the failing FlexCard or OmniScript, then click Assign.

Cause 2: The community profile lacks Apex class access to the OmniStudio controllers.

  1. Go to Setup > Users > Profiles and open the community profile assigned to the affected users.

  2. Click Enabled Apex Class Access > Edit.

  3. Add the controllers used by the runtime: OmniStudioBaseController, and for course-registration, the CourseRegistrationConnect controller.

  4. Move them to Enabled Apex Classes and click Save.

Cause 3: The community profile lacks object and field-level access used by the OmniScript or Integration Procedure data sources.

  1. Go to Setup > Object Manager and open each object the OmniScript/Integration Procedure reads or writes (for example, Product2, Quote, QuoteLineItem, or your course-offering object).

  2. On the community profile, set Object Permissions to Read for objects the process only reads, and Read plus Edit or Create for objects the process writes.

  3. Under Field-Level Security, set every field referenced by the OmniScript, FlexCard, or formula to Visible. Note: A hidden required field will produce the 403 INSUFFICIENT_ACCESS response.

Cause 4: The OmniStudio metadata/runtime is enabled but the site is still using cached component definitions.

  1. Go to Setup > Feature Settings > OmniStudio > OmniStudio Settings and confirm Enable OmniStudio Metadata is checked.

  2. Open the OmniScript or FlexCard in the OmniStudio designer, click Activate (and Compile for LWC if the component is LWC-based).

  3. Publish the Experience Cloud site again from Experience Builder > Publish.

Verification

Confirm the issue is resolved by logging in as the affected community user and opening the Experience Cloud page that runs the FlexCard or OmniScript. Verify the component loads and completes successfully with no "This feature is not currently enabled for this user" toast and no 403 errors in the browser network tab.

Knowledge-artikkelin numero

005389030

 
Ladataan
Salesforce Help | Article