---
schema_version: "1"
id: b2872ba08fb5070904e6a340cfffc759ae6d6b285fdaa04ab132dfeec0507703
title: Standard Omnistudio Content and Runtime
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_standard_omnistudio_content_and_runtime.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_standard_omnistudio_content_and_runtime.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 83cef06278d1377e7cb290238e5c5c26c5fe00b828a2e27f851e9a06ed8dd630
description: With the Omnistudio permission set license, standard Omnistudio content runs in standard runtime. From the Lightning App and Experience Builders, add standard content to a Lightning or Experience Cloud site with standard Omniscript and Flexcard components. Standard Omnistudio components built by Salesforce Industries, such as Health Cloud and Financial Services Cloud, are available. You can also use standard components instead of custom-generated components to run custom content in the standard runtime.
products:
  - Omnistudio
release: "264"
---
# Standard Omnistudio Content and Runtime

With the Omnistudio permission set license, standard Omnistudio content runs in standard runtime. From the Lightning App and Experience Builders, add standard content to a Lightning or Experience Cloud site with standard Omniscript and Flexcard components. Standard Omnistudio components built by Salesforce Industries, such as Health Cloud and Financial Services Cloud, are available. You can also use standard components instead of custom-generated components to run custom content in the standard runtime.

## Accessing Standard Content

Standard Omnistudio content is visible in the Omnistudio product home screens along with your custom Omnistudio content. However, we recommend that you use the standard Flexcard and Omniscript components to a Lightning page or an Experience Builder page after activation.

## Disabling Managed Package Runtime

We recommend rebuilding Omnistudio for Managed Package components using Salesforce standard components for these reasons:

- Components created in Omnistudio for Managed Package don’t always work as expected in Omnistudio Standard.
- If you edit Omnistudio for Managed Package components after switching to the standard runtime, your changes aren’t reflected in your site.

After activation, use the Lightning App Builder or Experience Builder to add the standard Flexcard or Omniscript component to a Lightning page or Aura-based Experience site. You can now add Omniscripts to LWR sites. See [Add Your Omniscript to an Experience Cloud Page](https://help.salesforce.com/s/articleView?id=xcloud.os_add_your_omniscript_to_an_experience_page_19992.htm&release=264.0.0&type=5 "In the Omnistudio standard runtime, add the standard Omniscript component to an Experience Builder page after activation.").

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio-264-0-0-production-enus/f526eaa8-ae05-487a-8944-4bb99b0b78ac/images/icon_important.png)

Important To embed a Flexcard in an LWR Experience site, keep the Managed Package Runtime setting enabled and use the generated LWC.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio-264-0-0-production-enus/f526eaa8-ae05-487a-8944-4bb99b0b78ac/images/icon_important.png)

Important Standard runtime enforces field-level security (FLS) more strictly than the managed package runtime. Before disabling Managed Package Runtime, verify that FLS is explicitly set for **Omni Process Compilation**, **Omni Data Transformation**, and **Omniscript Saved Sessions**. See [Disable the Managed Package Runtime and Deploy Custom Lightning Web Components](https://help.salesforce.com/s/articleView?id=xcloud.os_enable_standard_omnistudio_runtime.htm&type=5&language=en_US).

To maintain backward compatibility with existing pages referencing Omniscript and Flexcard LWCs, LWCs that existed before disabling Managed Package Runtime (formerly enabling Standard Omnistudio Runtime) will run in standard runtime the next time they’re reactivated.

## Viewing and Modifying Standard Content

- To let end users view a standard Flexcard or Omniscript in a Lightning page or Experience site, disable the Managed Package Runtime setting and confirm you have the Omnistudio permission set license.
- As an admin, to view and modify standard content in the designers, disable the Managed Package Runtime setting and install the Winter ’23 or later managed package.
    
    To modify standard components that ship with your Salesforce Industries license, you must create a version. Release updates are pushed to Version 1 of the components and are never editable. Your created version doesn’t update with new releases.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio-264-0-0-production-enus/f526eaa8-ae05-487a-8944-4bb99b0b78ac/images/icon_note.png)

Note Omnistudio doesn't support the **Load Lightning Experience in LWR** checkbox in Setup > User > Edit. If you use Omnistudio in your org, disable this setting. Disabling this setting doesn't affect Omniscripts and Flexcards embedded on your LWR sites.

- **[View, Modify, and Enable Fast Activation on Omnistudio Content](https://help.salesforce.com/s/articleView?id=xcloud.os_enable_fast_activation_on_omnistudio_content.htm&release=264.0.0&type=5)**  
    When you disable the Managed Package Runtime setting, you can view and modify standard Omnistudio content that ships with your Salesforce Industries license from the designers. You also enable faster Omniscript and Flexcard activation.

#### See Also

- [Disable the Managed Package Runtime and Deploy Custom Lightning Web Components](https://help.salesforce.com/s/articleView?id=xcloud.os_enable_standard_omnistudio_runtime.htm&type=5&language=en_US)
- [Activate and Publish a Flexcard](https://help.salesforce.com/s/articleView?id=xcloud.os_activateconfigureand_publish_flexcards_24744.htm&release=264.0.0&type=5 "After you confirm that the Flexcard is ready, activate it. After activation, add the Flexcard to a Lightning page or to a page in an Experience Builder site.")