---
schema_version: "1"
id: 9e31bd9ba61967d27b1ec1249910d79696b65391b03365ab054192d594746a07
title: Configuring Card Layout Properties (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_configuring_card_layout_properties.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_configuring_card_layout_properties.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 851ae2355896aa4483342674c59381072ab3333c355cff46bc588e81a2cfb153
description: For the managed package runtime, configure card layout properties.
products:
  - Omnistudio
release: "264"
---
# Configuring Card Layout Properties (Managed Package)

For the managed package runtime, configure card layout properties.

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

After creating a card layout, configure layout properties in the Layout pane of the Card Designer. See [Creating a Card Layout Using Card Designer (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_creating_a_card_layout_using_card_designer.htm&release=264.0.0&type=5 "For the managed package runtime, create a card layout to build visual components to your customer interactions by adding data, enabling actions, and using custom or Vlocity templates to determine the look and feel."). See [Creating an LWC Card Layout (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_creating_an_lwc_card_layout.htm&release=264.0.0&type=5 "For the managed package runtime, create an LWC card layout to enable Vlocity Lightning web components.").

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col>
          <col>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d342306e65">
              <p style="margin-bottom:0;">Property</p>
            </th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d342306e71">
              <p style="margin-bottom:0;">Description</p>
            </th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d342306e77">
              <p style="margin-bottom:0;">Example</p>
            </th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Property" class="slds-cell-wrap" style="vertical-align:top;" headers="d342306e65 ">
              <p style="margin-bottom:0;">+Add Metatags</p>
            </td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d342306e71 ">
              <p>Enables search engine optimization (SEO) options in your metadata by allowing the layout to write metatags to a page header.</p>
              <p>Available card metatags are: author, description, keywords, and viewport.</p>
              <p>The metatags are inserted after a layout or card loads, whether or not the data source is set.</p>
              <p style="margin-bottom:0;">Vlocity recommends that you replace metatags with the same name. Do not duplicate metatags. Web crawlers ignore duplicate tags.</p>
            </td>

            <td data-label="Example" class="slds-cell-wrap" style="vertical-align:top;" headers="d342306e77 ">
              <p style="margin-bottom:0;">For example, possible keywords for a card layout that shows a list of active account cases are <kbd>cases, current cases</kbd>, <strong class="uicontrol">active cases</strong>.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Property" class="slds-cell-wrap" style="vertical-align:top;" headers="d342306e65 ">
              <p style="margin-bottom:0;">
                <strong class="uicontrol">+Add Test Variables</strong>
              </p>
            </td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d342306e71 ">
              <p style="margin-bottom:0;">Returns test data after configuring your data source. <strong class="uicontrol">Name</strong> and <strong class="uicontrol">Value</strong> populate the dynamic fields in a data source endpoint. Enter the name of the variable to test, such as <kbd>params.id</kbd>. Enter the value of the variable. For more information on test variables and their settings, see <a href="https://help.salesforce.com/s/articleView?id=xcloud.os_testing_data_source_settings.htm&amp;release=264.0.0&amp;type=5" title="For the managed package runtime, add runtime variables to fetch and test your data source.">Testing Data Source Settings</a>.</p>
            </td>

            <td data-label="Example" class="slds-cell-wrap" style="vertical-align:top;" headers="d342306e77 ">
              <ul>
                <li>
                  <p><strong class="uicontrol">Name</strong>: For example, enter <kbd>params.id</kbd> to get the ID in a page parameter for a record, such as an account record ID.</p>
                </li>

                <li>
                  <p><strong class="uicontrol">Value</strong>: For example, enter the account ID found in the URL parameter of an account record.</p>
                </li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Property" class="slds-cell-wrap" style="vertical-align:top;" headers="d342306e65 ">
              <p style="margin-bottom:0;">
                <strong class="uicontrol">Add Session Variables</strong>
              </p>
            </td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d342306e71 ">
              <p style="margin-bottom:0;">Sets card layout attributes. Enter a variable <strong class="uicontrol">Name</strong> and <strong class="uicontrol">Value</strong> for each attribute.</p>
            </td>

            <td data-label="Example" class="slds-cell-wrap" style="vertical-align:top;" headers="d342306e77 ">
              <p style="margin-bottom:0;">For example, the layout template <code>cardCanvasLayout</code> has a configurable attribute called <code>title</code>, which adds a title to the top of the layout. Enter <kbd>title</kbd> in the <strong class="uicontrol">Name</strong> field and a value for the title such as <kbd>List of Accounts</kbd> in the <strong class="uicontrol">Value</strong> field.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Property" class="slds-cell-wrap" style="vertical-align:top;" headers="d342306e65 ">
              <p style="margin-bottom:0;">
                <strong class="uicontrol">Data Source</strong>
              </p>
            </td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d342306e71 ">
              <p>Sets a data source for the layout.</p>
              <p style="margin-bottom:0;">The data source holds the master query that returns results in a JSON structure for cards in the layout. For more information on how to configure a data source and to see a complete list of data sources, see <a href="https://help.salesforce.com/s/articleView?id=xcloud.os_configuring_data_sources_for_cards_components.htm&amp;release=264.0.0&amp;type=5" title="For the managed package runtime, configure a data source on a card, layout, or flyout to retrieve data from a Salesforce object or an external database. Display the returned data on cards in a layout or flyout.">Configuring Data Sources</a>. Cards can have data sources different from the layout data source.</p>
            </td>

            <td data-label="Example" class="slds-cell-wrap" style="vertical-align:top;" headers="d342306e77 ">
              <p style="margin-bottom:0;">For example, you might query every policy associated with an account, then create a card for each policy type.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Property" class="slds-cell-wrap" style="vertical-align:top;" headers="d342306e65 ">
              <p style="margin-bottom:0;">
                <strong class="uicontrol">Required Permissions</strong>
              </p>
            </td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d342306e71 ">
              <p>Limits user access to a card layout by entering a comma-separated list of custom permissions. If this field is left empty, any user can see the layout. See <a href="https://help.salesforce.com/articleView?id=custom_perms_overview.htm&amp;amp;type=5&amp;language=en_US" target="_blank">Custom Permissions</a>.</p>
              <p>This feature is available beginning with Vlocity Insurance and Health Winter '20 and Vlocity CME Winter '20.</p>
              <p style="margin-bottom:0;">Also see <a href="https://help.salesforce.com/s/articleView?id=xcloud.os_limit_user_access_to_a_card_layout_in_a_managed_package.htm&amp;release=264.0.0&amp;type=5" title="For the managed package runtime, in the managed package in your org, the VlocityRequiredPermissionCheck&nbsp;Apex Class must exist in Setup > Apex Classes for the Required Permissions feature to work. The Required Permissions feature enables you to limit user access to a card layout. Enter a list of custom permissions to specify which users can see your layout.">Limit User Access to a Card Layout in a Managed Package (Managed Package)</a>.</p>
            </td>

            <td data-label="Example" class="slds-cell-wrap" style="vertical-align:top;" headers="d342306e77 ">
              <p style="margin-bottom:0;">For example, enter <kbd>Can_Edit_Card,Can_View_Card</kbd> to only allow users with at least one of these custom permissions to see the card layout.</p>
            </td>

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