Current limitations of team-shared shared connections: Team-shared shared connections are available for use in compare and deploy, validation jobs, unit testing jobs, change monitoring 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 shared with 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.

When a team owner creates a Salesforce org connection, they can elect to create a team-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.

Note: We recommend using a service account for team-shared Salesforce org connections. All actions taken by Gearset using this connection will be done under this user.

Once the team-shared connection is enabled, connect your org as usual.

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.

A service account is used to perform Salesforce actions on behalf of a team.

A service account is a type of account that is not tied to an individual human user.

Service accounts are used when the credentials must be set up and maintained without being impacted by changes in the team.

This account is created and managed outside of Gearset in your Salesforce Org.

A personal connection is where the account is linked to a named individual connected to a human user on the team.

These are unique for each user on the team.

​