Salesforce admins and developers work on the same org but make changes in different ways. Lifecycle Center provides a shared space for both roles without changing how either works.
Required Editions
| Available in: Lightning Experience in Professional (API access required), Enterprise, Performance, Unlimited, and Developer Editions |
| Available in: Government Cloud Plus as interoperable. Turning on DevOps Center (Managed Package) in Government Cloud Plus orgs can send data outside the authorization boundary. Contact your Salesforce account executive for more details. Lifecycle Center is not available in Government Cloud Plus. |
| Not available in: EU Operating Zone. EU Operating zone is a special paid offering that provides an enhanced level of data residency commitment. Lifecycle Center is supported in orgs in the EU that aren’t part of EU OZ, per standard product terms and conditions. |
Admins make declarative changes, such as changes to page layouts, flows, fields, validation rules, using Salesforce UI. Developers make programmatic changes, including Apex classes, Lightning Web Components, and custom changes, using Agentforce or CLI tools. DX Inspector and Lifecycle Center track both types of changes as work items and move them through the same pipeline to production.
Developer Changes in Lifecycle Center
Developers who use CLI tools, Agentforce Vibes, or work directly in their source control repository don’t need to change how they work. Lifecycle Center automatically detects these external changes and reflects them in the pipeline through VCS sync and background sync. You don’t need to act when a developer works outside of Lifecycle Center.
Conflicts
The most common source of conflicts between admins and developers is modifying the same metadata components at the same time. When this conflict happens, Lifecycle Center detects the conflict and proposes a solution using Lifecycle Center Model Context Protocol (MCP) tools before it reaches production.
You can avoid most conflicts by notifying your team before you start working on a work item or a component that others might also be modifying. A quick check at the start of the development activity helps solve merge conflicts issues.
Sync Your Pipeline
Use the pipeline as your team’s shared view. Before you promote changes, check which other work items are in the same stage and who owns them. If any of the work items update the shared components, discuss with your team and avoid merge conflicts later.