Lightning Communities Developer Guide

Get Up to Speed with Lightning Communities
Develop Lightning Communities: The Basics
Customize the Look and Feel of a Lightning Template
Example: Build a Condensed Theme Layout Component
Develop Secure Code: Lightning Locker and Stricter CSP
Analyze and Improve Community Performance
Connect Your Community to Your Content Management System
Report on Deflections: The Deflection Signals Framework
Deploy a Community from Sandbox to Production
Deploy Your Community with Change Sets
Considerations for Deploying Communities with Change Sets
Deploy Your Community with the Metadata API
ExperienceBundle for Lightning Communities (Developer Preview)
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Deploy Your Community with Change Sets

Use change sets to move your community between related orgs that have a deployment connection, such as your sandbox and production orgs. Create, customize, and test your community in your test environment and then migrate the community to production when testing is complete.
Available in: Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Enterprise, Performance, and UnlimitedEditions

User Permissions Needed
To customize or publish a community: Create and Set Up Communities
To edit deployment connections and use inbound change sets: Deploy Change Sets AND Modify All Data

If a user requires access only to metadata for deployments, you can enable the Modify Metadata Through Metadata API Functions permission. This permission gives such users the access they need for deployments without providing access to org data. For details, see “Modify Metadata Through Metadata API Functions Permission” in Salesforce Help.

Note
To use outbound change sets: Create and Upload Change Sets, Create AppExchange Packages, AND Upload AppExchange Packages

You can use change sets to move Lightning communities and Salesforce Tabs + Visualforce communities using the Network component type.

  1. Create and test your community in your preferred test org, such as sandbox.
  2. From Setup in your test org, enter Outbound Change Sets in the Quick Find box, and then select Outbound Change Sets.
  3. Create a change set, and click Add in the Change Set Components section.
  4. Select the Network component type, choose your community, and then click Add to Change Set.
  5. To add dependent items, click View/Add Dependencies. We recommend selecting all the dependencies listed.
    • For navigation menus that link to standard objects, custom list views aren’t included as dependencies. Manually add the custom list view to your change list.
    • Manually add new or modified profiles or permission sets referenced in Administration | Members.
    • The list of dependencies has two Site.com items—MyCommunityName and MyCommunityName1. MyCommunityName holds the various Visualforce pages that you can set in Administration (in Community Workspaces or Community Management). MyCommunityName1 includes the pages from Community Builder.

    Tip

  6. Click Upload and select your target org, such as production.
    Make sure that the target org allows inbound connections. The inbound and outbound orgs must have a deployment connection.
  7. From Setup, select Inbound Change Sets and find the change set that you uploaded from your source org.
  8. Validate and deploy the change set to make it available in the target org.

    When you deploy an inbound change set, it overwrites the community in the target org.

    Warning

  9. Manually reconfigure any unsupported items in the target org community.
  10. Add data for your community, and test it to make sure that everything works as expected. Then publish your changes to go live.