---
schema_version: "1"
id: 4ae315ec861ffdb276af002355540778de5a8711a9184e39409383f772dd57d7
title: Deploy Additional Metadata for Consumer Goods Cloud Managed Packages
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/cg_task_deploying_additional_metadata.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.cg_task_deploying_additional_metadata.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: fb01a681d55d024683472fcf7bbf895ab9074af28e020d178d5ea626503edb13
description: Download unmanaged permission sets and approval processes from the additional metadata folder in Static Resources. Set up approval processes for custom objects; and get object and field permissions for standard and custom objects using the unmanaged permission sets.
products:
  - Consumer Goods
release: "264"
---
# Deploy Additional Metadata for Consumer Goods Cloud Managed Packages

Download unmanaged permission sets and approval processes from the additional metadata folder in Static Resources. Set up approval processes for custom objects; and get object and field permissions for standard and custom objects using the unmanaged permission sets.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
        <colgroup>
          <col>
        </colgroup>
        <tbody>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">
              <p>Available in: Lightning Experience </p>
              <p style="margin-bottom:0;">Available in: <strong>Enterprise</strong> and
                <strong>Unlimited</strong> Editions where Consumer Goods Cloud is enabled
              </p>
            </td>

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

Install Salesforce CLI and authorize it for use with your Salesforce org using the command: `sf org login web --alias ALIAS`

Here are the steps to deploy additional metadata:

If you're an upgrade customer, to prevent overwriting your customizations to the existing approval processes and permission sets, we recommend cloning them before deployment of additional metadata. Post deployment, keep the deployed unmanaged metadata inactive, use it as a reference, and make the required changes manually to your cloned version. Post applying the changes on the cloned version of permission sets and approval processes, make sure to activate the approval processes. You can skip cloning and apply the changes manually if you don’t have any customizations made.

To deploy additional metadata:

1. From Setup, in the Quick Find box, find and select **Static Resources**.
2. Deploy the cgcloud\_\_additional\_metadata file. The downloaded cgcloud\_\_additional\_metadata file contains another .zip file in it.
    1. For Windows users, after you extract the cgcloud\_\_additional\_metadata.zip file, you can see another zip file named additionalMetadata.zip. Extract this file. You can see these folders: permissionsets, approvalProcesses, and a new file named package.xml. Add both the folders and the package.xml file into a new folder named additionalMetadata.
    2. For Mac users, after you extract the zip file, a new folder named additionalMetadata is available after the extraction.
3. From the command prompt, go to the folder that contains the additionalMetadata folder.
4. Deploy the additionalMetadata folder by using this Salesforce CLI command:`sf project deploy start --metadata-dir additionalMetadata --target-org ALIAS --wait 5`
    
    During deployment, unmanaged permission sets and approval processes are created.
    
    ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-consumer_goods_retail_admin-264-0-0-production-enus/5bb7d7f5-119d-42d0-8596-95e762837019/images/icon_important.png)
    
    Important Group: All Internal Users is the default value in the Initial Submitter field for approval processes of Orders and Customer Tasks. Any user other than the creator can submit the order or task for approval. Review the approval processes and if necessary, tailor them based on business needs. We recommend keeping the Initial Submitters field as Group: All Internal Users for the approval processes. See [Specify Who Can Submit Records to an Approval Process](https://help.salesforce.com/s/articleView?id=platform.approvals_create_submitters.htm&type=5&language=en_US).
    
    If you're new to Summer ’25, turn on the CGCloud: Order Approval for Mobility Flow. This starts the approval process for orders that are created and synced from the Consumer Goods Cloud offline mobile app.
    
    If you’re ‌upgrading to Summer ’25, in Approval Processes under Setup, review the Initial Submitter field and update the Initial Submitters field from Record Creator to Group: All Internal Users for Orders and Customer Tasks.

Check the metadata deployed in your org. For example, to verify whether the permission sets are deployed, from Setup, find and search for permission sets, and then check whether the new permission sets are available.

- **[Approval Processes for Direct Store Delivery (DSD) and Van Sales](https://help.salesforce.com/s/articleView?id=ind.cg_reference_dsd_approval_process.htm&release=264.0.0&type=5)**  
    Similar to Retail Execution orders, all Direct Store Delivery and Van Sales orders are set to Ready status after drivers complete their order on the offline mobile app and the order's approval processes are completed. Here are considerations made while setting up direct approval processes of the Advance Orders object shipped as part of Static Resources for Direct Store Delivery and Van Sales.

#### See Also

- [Install the CLI on Mac OS](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_install_cli.htm#sfdx_setup_install_cli_macos)
- [Salesforce auth Commands](https://developer.salesforce.com/docs/atlas.en-us.212.0.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_force_auth.htm)