---
schema_version: "1"
id: 706ebf221ef1817ced3ed2b116bf6840116cdf85f729764598836c9d56ec8512
title: Add your Omniscript to a Lightning Page (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_add_your_omniscript_to_a_lightning_page.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_add_your_omniscript_to_a_lightning_page.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a2339d7b10f4dd4543c362ad0628c8fc68332760b982a1ad98e95db3dd38b80c
description: For the managed package runtime, add your Omniscript to a Salesforce Lightning page.
products:
  - Omnistudio
release: "264"
---
# Add your Omniscript to a Lightning Page (Managed Package)

For the managed package runtime, add your Omniscript to a Salesforce Lightning page.

![Managed Package app icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/resources-global/_corporate/images/managedpackageicon.png) This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see [Omnistudio Help](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_standard.htm&language=en_US).

1. In a Lightning Page's App Builder, search for the name of your Omniscript by entering the Omniscript's unique Type, SubType, and Language. Use the syntax **Type/SubType/Language** to search as the search does not ignore forward slashes.
    
    ![The name of an LWC OmniScript component as it appears in Community and Lightning component lists.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/omnistudio_for_managed_packages/images/component_name_os.png)
2. Drag the component into the Lightning Page.
    
    In the Lightning App Builder, Omniscripts aren't available in the Components section when page type is Home Page. Omniscripts are available for Record Page, App Page, Community Default, and Community Page types.
3. (Optional) Apply Newport styling by entering **newport** into the layout field in the component's properties panel. Lightning styling is the default styling when the layout property is blank.
    
    ![The Lightning and Newport layout options for an LWC OmniScript component.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/omnistudio_for_managed_packages/images/lightning_os_layout.png)
4. (Optional) Configure the inline options. See [Display Inline Omniscripts on Lightning and Community Pages (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_display_inline_omniscripts_on_lightning_and_community_pages.htm&release=264.0.0&type=5 "For the managed package runtime, enable LWC Omniscripts to run inline without leaving the context of a page. An inline Omniscript renders as a button that, when clicked, launches the Omniscript inline. The record id of a page passes into an inline Omniscript as a Context Id automatically. You can render more than one inline Omniscript on a page beginning in Vlocity Insurance and Health Summer '20 and CME Fall '20 .").
5. (Optional) Control how right-to-left languages display. Omniscript provides beta support for right-to-left languages. In the **dir** field, select whether the Omniscript displays ltr or rtl. Available beginning with Vlocity Insurance and Health and Vlocity CME Summer '20
6. (Optional) Modify the component's visibility by adding filters. For more information, see [Dynamic Pages](https://help.salesforce.com/articleView?id=lightning_page_components_visibility.htm&type=5&language=en_US).
7. (Optional) Change the device view of the App Builder to Phone to see how the Omniscript displays on a mobile device. Available beginning with Vlocity Insurance and Health and Vlocity CME Summer '20