Skip to content

Install Salesforce DevOps Center

You need to install Salesforce DevOps Center before you can use it. It’s delivered as a managed package that you can install in a sandbox or production org using the provided installation URL. In this blog, we discuss how to install Salesforce DevOps Center step-by-step.

How to Install the DevOps Center Package

To install DevOps Center in your Salesforce org, you need a production org with Professional, Enterprise, or Unlimited edition, or a new Developer edition org (or created after summer 2022):

  1. Go to Setup and enter DevOps Center in the Quick Find Box. Select DevOps Center.
  2. Click the toggle to enable DevOps Center.
  3. Click “Install Package.”
  4. Follow the instructions to install DevOps Center.
  5. Select Install for Admins Only ) or Install for All Users.
  6. Approve third-party access to and
  7. Click “Done.”

You’ll receive a confirmation email when the installation is complete. When in doubt, confirm the installation on the Installed Packages Setup page.

You might get an error message when trying to install DevOps Center in a Professional Edition org. An unforeseen issue occurs when the post-installation script runs.  Currently, there’s no workaround for this issue. However, you can install DevOps Center in another supported org edition, like Developer Edition. Salesforce plans to fix this issue in a near-future release. 

Add User to the DevOps Center Org

If there are team members who aren’t yet users in the DevOps Center org, add them. Each team member must have the appropriate license and profile based on their role:




Project Manager

Release Manager

Anyone who adds and manages environments in DevOps Center


Standard User

Team members

Salesforce Limited Access – Free

Limited Access User

These licenses and profiles are the minimum for each type of user. You can also provide team members with a more fully featured license or profile if needed.

Here’s how to add users to the org:

  1. Log into the DevOps Center org.
  2. From Setup, search for “Users” and select it.
  3. Click “New User” or “Add Multiple Users.”
  4. Select the appropriate license type and profile for each user based on their role.
  5. Select “Generate passwords and notify user via email.”
  6. Click “Save.”

Your team members will receive an email inviting them to use the org, but since you’re still setting up DevOps Center, they can’t do anything in it. It’s advisable to ask your team to wait until you’ve completed the setup before they log in. 


Assign the DevOps center Permission Sets Appropriately

  • When working on a Salesforce project, you’ll need a team consisting of a variety of roles. Salesforce recommends the following team roles:
  • Team manager/Project manager
  • Org admin
  • Admin/Declarative developer
  • Pro-code developer
  • Release manager
  • Environments manager
  • Quality assurance specialist
  • Business Owner

Depending on their role, each team member needs their own specific permission sets. When assigning permission sets, consider who only needs access to work items and who needs to change project-level settings.

DevOps Center Permission Sets


Permission Set


DevOps Center

This is the base permission set for DevOps Center that provides the permissions and data access users need to manage customizations for work items. 

Users with this permission set have the ability to view all connected environments and pipelines.

This permission set doesn’t overlap with the DevOps Center Manager permission set.

Assign to all DevOps Center users, including team members who have the DevOps Center Manager permission set.

DevOps Center Manager

This permission set provides the permissions and data access users need to set up projects, environments, and users.

Assign to team or project managers.

DevOps Center Release Manager

This permission set provides permissions to promote changes through the pipeline.

Assign to the release manager.


This permission set allows managers of DevOps Center projects to manage the connections to work environments. It includes the Modify Metadata Through Metadata API Functions and Customize Application user permissions that allow the manager to create NamedCredential records.

Assign to team or project managers.


This permission set grants access to the named credentials users need to authenticate to environments. It’s automatically created and maintained by DevOps Center.

Assign to all DevOps Center users. 

Assign the DevOps Center and sf_devops_NamedCredentials permission sets to all users:

  1. In Setup, search for “Permission Sets” and select it.
  2. Choose the DevOps Center permission set.
  3. Click “Manage Assignments.”
  4. Click “Add Assignments.”
  5. Select the users you want to assign the permission set and click “Assign.”
  6. Click “Done.”
  7. Repeat this process for the sf_devops_NamedCredentials permission set.


Use the same procedure to assign the DevOps Center Manager and DevOps Center Release Manager permission sets to users who’ll be configuring projects, building pipelines, and promoting changes through the release pipeline.

The Set Up Workflow

Because you’re the admin of the DevOps Center org, you’re in charge of adding users, setting up projects, adding environments, configuring the pipeline, and creating work items.

The setup workflow is as follows:

Create sandboxes and project repository > Open DevOps Center > Create a new project and connect to repository > Connect to the final release environment > Add the other environments needed for the project > Configure the pipeline > Add users to the repository > Add users to the DevOps Center org > Assign permission sets to the users > Create and assign Work Items > Bring team members into the DevOps Center org

Create a GitHub Account

Every DevOps Center project needs its own repository or repo to store project work files and changes. During the project, the repository is your team’s centralized source of truth to manage changes. 

For the public beta, DevOps Center only integrates with GitHub as a source control system. After GA, Salesforce plans to add other third-party source control systems, including GitLab, GitHub, and Bitbucket.

Everyone working on the project needs their own GitHub-hosted, cloud-based account. You can sign up for one here. 

Sign up for weekly insights on Salesforce DevOps!

Powered by