Unify Logo Footer.svg
Platform Tools
Logo
Creating an outbound change set

Creating an outbound change set

Logo

4 mins READ

Building the bundle of changes you want to send from this environment.

Overview

Go to Change Sets › Outbound and create a new change set. Building it is a three-step flow — Change Set SettingsSelect Assets to Import, and Review Change Set. In settings you give it a name and optional description and choose how it will be delivered (a Move to a connected environment, or an Export file you transfer yourself); then you select the assets to include — as you do, the platform gathers their dependencies for you. On review you can save as draft or submit — Submit for Approval for a Move, Save & Export for an Export — which packages everything and either pushes it to the destination or produces the export file. Until you submit, the change set stays editable in Draft; afterwards the review tab becomes a read-only Change Set Summary.

Where: Change Sets › Outbound › create

Screenshot 2026-08-31 at 17.25.04 1.png
Screenshot 2026-08-31 at 17.25.04 1.png

Choosing which assets to include

On the Select Assets step, assets are organized by type (Automations, Objects, Connections, Templates, and so on) under groups like Workflows, Applications, Objects, Agentic AI, and Platform Tools. Browse or search within a type — or use Select by tag — and tick the ones that changed. You can include assets from several types in one change set. For each asset you can view its dependencies (what it needs to work) before adding — and those dependencies are added automatically so the bundle is complete. For Objects, only the schema is exported by default; a Data Selection dropdown lets you also include records — No Records (Only Schema)All Records, or Filtered Records matching conditions you set. You don't need to hunt down every connection or template by hand; pick the things you actually changed and let dependency resolution complete the set.

Where: Outbound change set › Select Assets

Screenshot 2026-08-31 at 17.25.14 1.png
Screenshot 2026-08-31 at 17.25.14 1.png

Where I change a change set's name, description, or destinations later

While the change set is in Draft, open its Change Set Settings tab to edit its name, description, type (Move or Export), the destination environments (for Move), and the password/encryption (for Export). Once you submit, the change set becomes read-only in the source environment — its contents are locked so what was shipped can't change underneath the destinations. So make your edits before submitting; after that, create a new change set for further changes.

Where: Outbound change set › Change Set Settings

FAQs

What can I configure on a connection, and can I share it?

Opening a connected environment shows settings that govern change sets arriving from it:

  • Approval Type — Auto-Approval (the default: incoming change sets are imported automatically, no review) or Manual Approval (change sets wait for review before importing).

  • With Manual Approval, an Approval Flow — one or more approval levels, each with a level name, a number of approvals required (1–6), and the approvers (users and/or teams) who can sign off.

  • With Auto-Approval, a Deployment Type — Update Records (update assets that already exist, the default) or Skip Records (leave existing assets untouched).

  • Retain Role Mapping — copy valid team and role mappings from the source environment (anything missing in the destination is skipped).

  • Retain Asset Owner — preserve who owns each asset during import, with a matching property to match user identities across environments and JIT provisioning (auto-create a missing user, or map ownership to whoever deploys).

You can also Share a connected environment with other users or teams so more than one person can promote through it. Configure approvals on the connections into your sensitive environments (so promotions to production are reviewed), and share connections with the people responsible for releases.

Where: Connected environments › details / Share