Should All Users Have Their Own Org Credential?

Please note: This article does not apply to the org credential of the organization where Copado is installed. Each user must own org credentials in the org where Copado is installed. This is a prerequisite.

Ideally, all users who work with Copado should have their own org credentials for each development environment they work in. But it can be very beneficial to establish default org credentials for environments as well. If you use Copado Continuous Delivery to automate or schedule deployments or back-promotions, those deployments normally use the org credentials for the user who created the story. Setting a default org credential allows Copado to perform deployments even if users don't have individual credentials for a particular environment. Default org credentials are also useful for tasks like taking Git Snapshots of an environment.

To enable an org credential as default, you only need to mark the Default Credential checkbox in the Org Credential record.



In addition to creating this default org credential, you have to ensure org credentials are shared properly. Since the Org Credential object is set as private in the Sharing Settings, only the owner of the record can view and edit it. 

To prevent Insufficient access on cross reference entity errors when using default org credentials, you need to make sure users have read/write access to the org credentials. You can do this using any of the options below:

  • The Share button in the Org Credential record.

  • Sharing rules for the Org Credential object.

  • The Modify All permission for the Org Credential object in the profile or permission set.

How did we do?