All Collections
Team account management
Team-owned shared Salesforce org connections
Team-owned shared Salesforce org connections

Create connections once and share them with your team

Mark Allan avatar
Written by Mark Allan
Updated over a week ago

Current limitations of team-owned shared connections: Team-owned shared connections are available for use in compare and deploy, validation jobs, unit testing jobs, data backup jobs and CI jobs. Support for data deployment is not yet available.

On larger teams, with members potentially joining and leaving on a regular basis, it can sometimes become onerous to maintain Salesforce org connections if they are set up by individual team members. In this case, team owners can instead create connections that are owned by the team rather than an individual and then share these connections with selected members. This feature is available for all customers on a Teams or Enterprise license.

Adding a team-owned shared connection

When a team owner creates a Salesforce org connection, they can elect to create a team-owned shared connection:

When you create a connection with this option selected, the connection is not owned by you but by the team, though as a team owner you still have full access to it. This means that it will continue to be available to all team members even if you leave the team in the future.

Using team-owned shared connections

When a shared connection is first created, it can only be used by team owners. However, for compare and deploy, access to the connection can be granted to team members as with any other org connection - see Sharing org credentials with team members.

Did this answer your question?