--- schema_version: "1" id: 926361bbf2960c58ae87ee3ca8c85d27f2220483c9d680f3274b87c38b5e491d title: Set Up Lifecycle Center collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/next_gen_devops_center_setup.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.next_gen_devops_center_setup.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 1ccc8b27cc9af78e66e1d9b73ef2c10d263ff2987957170ad7d403825b50db2f description: Configure Lifecycle Center (formerly next-generation DevOps Center) to manage your release management lifecycle. Review the prerequisites, access the feature, manage users, and set up your projects and pipelines. products: - Salesforce Platform release: "264" --- # Set Up Lifecycle Center Configure Lifecycle Center (formerly next-generation DevOps Center) to manage your release management lifecycle. Review the prerequisites, access the feature, manage users, and set up your projects and pipelines. Before you begin, review the [set up considerations](https://help.salesforce.com/s/articleView?id=platform.next_gen_devops_center_setup_considerations.htm&release=264.0.0&type=5 "Review these considerations before you set up Lifecycle Center.") and make sure that you have these resources: - A source control provider account. See [Creating an account on GitHub](https://docs.github.com/en/get-started/start-your-journey/creating-an-account-on-github) or [Sign up for a Bitbuck account](https://id.atlassian.com/login). - (Optional) To use Lifecycle Center Model Context Protocol (MCP) tools in the Salesforce DX MCP Server: - An MCP-enabled IDE, such as [Agentforce Vibes IDE](https://developer.salesforce.com/docs/platform/code-builder/overview) or VS Code. - A user-facing MCP client, such as the [Agentforce Vibes Extension](https://developer.salesforce.com/docs/platform/einstein-for-devs/guide/einstein-overview.html). For information about setting up DevOps Center using managed package, see [Install and Configure DevOps Center](https://help.salesforce.com/s/articleView?id=platform.devops_center_setup_install.htm&type=5&language=en_US). 1. **[Access Lifecycle Center](https://help.salesforce.com/s/articleView?id=platform.devops_center_enable_for_users.htm&release=264.0.0&type=5)** Lifecycle Center is enabled by default in your Salesforce org, so you don't have to turn it on. You can open it directly from the App Launcher. The first time you open it, accept the DX Tools terms and conditions. 2. **[Add Team Members as Users in the Lifecycle Center Hub Org](https://help.salesforce.com/s/articleView?id=platform.devops_center_add_team_members.htm&release=264.0.0&type=5)** Add any team members who need access to Lifecycle Center Hub org. For each team member, specify the appropriate license and profile based on their role. 3. **[Assign Lifecycle Center Permission Sets](https://help.salesforce.com/s/articleView?id=platform.devops_center_assign_permissions.htm&release=264.0.0&type=5)** Grant team members access to Lifecycle Center features and workflows by assigning the appropriate permission sets. 4. **[Source Control Setup](https://help.salesforce.com/s/articleView?id=platform.devops_center_source_control_setup.htm&release=264.0.0&type=5)** Lifecycle Center uses your source control as the single source of truth for all metadata and configuration data changes across your pipeline. A repository stores your project work files, including code, text, images, and so on. 5. **[Exclude Metadata with the .forceignore File](https://help.salesforce.com/s/articleView?id=platform.devops_center_exclude_metadata_with_forceignore.htm&release=264.0.0&type=5)** Use the .forceignore file to exclude files or metadata types that you don’t want to commit to the source control or deploy to the target org in your release pipeline. This file makes sure that DX Inspector and Lifecycle Center don’t push or pull unnecessary files, such as IDE configuration files, local test data, or specific profiles, from the development environment. 6. **[Create a Lifecycle Center Project](https://help.salesforce.com/s/articleView?id=platform.devops_center_create_project.htm&release=264.0.0&type=5)** Create a project to serve as the central workspace for your team’s change management collaboration. 7. **[Build Your Pipeline](https://help.salesforce.com/s/articleView?id=platform.devops_center_build_pipeline.htm&release=264.0.0&type=5)** Define the sequence of stages for your release lifecycle by building a pipeline in Lifecycle Center. 8. **[Create and Assign Work Items](https://help.salesforce.com/s/articleView?id=platform.devops_center_create_assign_work_items.htm&release=264.0.0&type=5)** Use work items to track the progress of changes related to specific objectives, such as user stories or issue fixes. Work items help teams manage changes and releases by providing visibility into the status and progress of changes. 9. **[Integrate Agentforce Vibes IDE with Lifecycle Center](https://help.salesforce.com/s/articleView?id=platform.devops_center_integrate_agentforce_vibes.htm&release=264.0.0&type=5)** Agentforce Vibes IDE provides a modern developer experience and comes with everything you need to work with Salesforce DX MCP Server and Lifecycle Center tools (previously DevOps Center tools). We recommend setting up Agentforce Vibes IDE if you want to experience the capabilities of the MCP server. #### See Also - [Access Lifecycle Center in a Scratch Org](https://help.salesforce.com/s/articleView?id=platform.devops_center_setup_install_scratch_org.htm&release=264.0.0&type=5 "Scratch orgs offer a temporary evaluation environment with a maximum duration of 30 days.")