Current limitations of team-shared shared connections: Team-shared shared connections are available for use in Compare and deploy, CI jobs, validation jobs, unit testing jobs, change monitoring jobs, and data backup 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.
Adding a team-shared shared connection
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. You can follow these guidelines if needed: Adding a Salesforce org connection via OAuth
Add a team-shared connection from already authorized org connection
If you already have a Salesforce org connection added to your Gearset account, and that org is showing up on your Salesforce orgs page under My org connections tab - click this button: 
and then select Add a team-shared connection.
You'll then see a pop up window.
Here, you need to type in your org's username in the window below (to match the username displayed in My org connections) in order for the blue Authorise button to become clickable.
After your org is converted to a team-shared org connection, you'll find it under Team-shared org connections tab.
Note: It is an expected behaviour for org connection that is changed to a team-shared connections to no longer show up under My org connections tab.
It is because adding a team-shared org connection this way simply establishes a completely new org connection in our app.
Using team-shared 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 - for more information, see this article: Sharing org credentials with team members.
What is a service account?
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.
What is a personal connection?
A personal connection is where the account is linked to a named individual connected to a human user on the team.
Personal org connections are unique for each user on the Gearset team.
FAQs
My team-shared org connection isn't showing on the Compare and deploy page.
My team-shared org connection isn't showing on the Compare and deploy page.
If you've converted an existing org connection to a team-shared org connection, and your team-shared org isn't instantly available under Salesforce authentication option on the Compare and deploy page - please try clearing your browser's cookies and cache, and re-log into our app.
This should resolve your issue.
Whose name shows on deployments made with team-shared org connections?
Whose name shows on deployments made with team-shared org connections?
In Salesforce, changes deployed via a Team-shared org connection will show as deployed by the user who created the connection, rather than the person doing the deployment. In Gearset, however, you will see who made each deployment on the Deployment history page.
If there are any other FAQs you'd like us to cover in this article, feel free to reach out to us via in-app chat to let us know. Thank you!