A user attempts to launch an OmniScript from a record page, but an error message...

If the user already has OmniScript runtime access, the next security issue to investigate is access to the underlying Apex classes used by OmniStudio runtime operations, Data Mappers, Integration Procedures, or Remote Actions. Salesforce’s OmniStudio security checks include Apex class access enforcement, especially where Remote Actions or managed package classes are involved. Save Options would affect how data is saved, not whether the Lightning component can be accessed. Multi-language settings do not cause a permission-to-access-component error. FlexCard permissions are not the most likely cause when the problem occurs while launching an OmniScript. Therefore, the developer should verify the user’s permission sets/profile grant access to the Apex classes required by the OmniScript’s runtime and called actions.

================