Copado Base Setup and Implementation

Updated 4 weeks ago by Copado Solutions

Getting ready to implement Copado? This article lists several items that you need to take care of when rolling out Copado in your organization.

Users and Licenses

In this section we will go over the licenses and user permission sets required to start working with Coapdo:

  1. The first thing you need in order to start using Copado are Salesforce licenses for the users that will be using Copado. You can find all the information about the required Salesforce licenses in the article What Salesforce Licenses or Permissions Do I Need to Start Using Copado?
  2. Once you have the required Salesforce licenses, follow the steps below to assign Copado licenses and permissions to users and complete the Copado setup:
    1. Install Copado from the AppExchange.
    2. Create an org credential for each of the users that will be working with Copado in the org where Copado is installed.
    Each user needs to create an org credential for the org where Copado is installed. Otherwise, they won’t be able to use Copado properly.
    1. Create an API Key in order to enable the webhooks functionality, e.g. scheduling Copado jobs or allowing for custom automation of actions.
    2. If required, set up the sandbox environments that you will connect to Copado (sandboxes, developer, production orgs, e.g. dev1, dev2, int, UAT, etc) and then create org credentials for each of the orgs. To authenticate the org credential, sign in to each org with the corresponding user.
Please note that this last step can now be performed with the pipeline wizard.
  1. If you want to provide your developers with a more restrictive access to Copado, create a permission set that grants Copado access to the users that will work with Copado:
  • The Copado package provides the Copado User permission set with access to all Copado functionality. You can clone this permission set and customize it for other types of users (e.g. developers, QA, scrum master).
Please bear in mind that the license type will already restrict Copado Change Management users (no deployments to production, unable to create org differences, unable to create and execute snapshots, unable to create compliance rules, unable to create Selenium tests).
  1. If you have IP restrictions in your Salesforce org, make sure you whitelist the Copado static IP addresses in Setup > Security > Network Access.

Best Practices and Additional Configuration

Once you have successfully installed Copado and have all the required licenses and permissions to start working with Copado, it is recommended that you define a release process and then make the necessary changes to align Copado with your process.

Here are the suggested steps:

  1. Outline the steps you would like to follow starting when user stories are created and defined until they are released and move to upper environments:
  1. If your process includes review quality gates (e.g. business testing, peer review, documentation review, etc.) consider creating custom fields, validation rules and process builder flows to enforce those quality gates.
  2. Consider modifying the main layouts your users will be working with (e.g. user story, project, epic, sprint) and add or remove fields as required. Having a defined process will help you focus on what you need to modify.
  3. Leverage Copado Academy and organize training sessions for your users to get hands-on learning about Copado. Contact your customer success manager for more information about Copado Academy.
  4. Review the documentation and configure a list of useful articles your users can go through to learn how to accomplish the most frequent tasks they will be working on. Share this list with the team so that they can access it whenever needed.
    Developer and admin tasks usually include the following:

As each implementation of Copado is dependent on individual client requirements, a Copado expert can guide you and your team with a tailored implementation and best practices on release management for Salesforce. For more information, contact your customer success manager.


How did we do?