---
schema_version: "1"
id: ef3dc6e77db483983a0e47428ab4edade6aff2a765b9294256c6eead32cb57ee
title: Managed and Unmanaged Components in Managed Packages (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_managed_and_unmanaged_components_in_managed_packages.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_managed_and_unmanaged_components_in_managed_packages.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: d9a37a2ec171cd08b471b2af1f85f90167dbd9492e4b876e5d279ddd311f08e5
description: For the managed package runtime, managed Flexcard components visible in the Lighting App and Community Builders and shipped in the managed package in your org, work as-is. As in, you can add them to a Lightning or Community page without having to use the Flexcard Designer.
products:
  - Omnistudio
release: "264"
---
# Managed and Unmanaged Components in Managed Packages (Managed Package)

For the managed package runtime, managed Flexcard components visible in the Lighting App and Community Builders and shipped in the managed package in your org, work as-is. As in, you can add them to a Lightning or Community page without having to use the Flexcard Designer.

![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).

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png)

Note

A Managed Flexcard component is a component included in an org like those included in Express or vertical orgs on install. An Unmanaged Flexcard component is one you create.

If you want to modify the component, you must open the managed Flexcard in the Flexcard Designer. A managed component opened in the Flexcard Designer triggers the creation of an unmanaged component, which is an exact copy of the managed component. Changes to the Flexcard only affect the unmanaged version because the managed version can never be modified.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d164126e61">
              <p style="margin-bottom:0;">Required Versions</p>
            </th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Required Versions" class="slds-cell-wrap" style="vertical-align:top;" headers="d164126e61 ">
              <p style="margin-bottom:0;">Available beginning with Vlocity Health and Insurance Spring '21 .</p>
            </td>

          </tr>
        </tbody>
      </table>

## Find Unmanaged Components in Lightning App Builder

In the Lightning App Builder, the managed version is visible under the **Custom - Managed** section of the **Components** pane. The unmanaged version is visible under the **Custom** section of the **Components** pane. Both have the same name unless you change the **Master Label** of the unmanaged version in the **Publish Options** feature of the Flexcard Designer.

## Find Unmanaged Components in the Community Builder

In the Community Builder, both unmanaged and managed versions display next to each other in the Custom section of the Lightning Components Pane. Both have the same name. To distinguish the unmanaged component from the managed component, after activating the Flexcard in the Flexcard Designer, update the **Master Label** with the **Publish Options** feature.

## Child and Parent Managed and Unmanaged Components

This table describes how the managed and unmanaged components work with child and parent Flexcard components:

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d164126e146">
              <p style="margin-bottom:0;">Flexcard Type</p>
            </th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d164126e152">
              <p style="margin-bottom:0;">Description</p>
            </th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Flexcard Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d164126e146 ">
              <p style="margin-bottom:0;">Child, Parent</p>
            </td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d164126e152 ">
              <ul>
                <li>
                  <p>A parent and child component works as-is unless opened in the
                    Flexcard Designer</p>
                </li>

                <li>
                  <p>When a managed component is opened in Flexcard Designer, an
                    unmanaged component is generated as an exact copy, and changes
                    effect only the unmanaged component.</p>
                </li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Flexcard Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d164126e146 ">
              <p style="margin-bottom:0;">Child</p>
            </td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d164126e152 ">
              <p style="margin-bottom:0;">If a managed child component is opened in the Flexcard Designer, the
                parent component must also be opened in the Flexcard designer, if it is
                managed, so that an unmanaged version is generated.</p>
            </td>

          </tr>
        </tbody>
      </table>