License requirements to use team-shared Pipelines:
This feature is available for all customers using Deployment Teams and Automation Starter license, or any license above (e.g. Enterprise license).
Check our Pricing page for more information about different types of licenses.
On larger teams, with members potentially joining and leaving on a regular basis, it can sometimes cause administrative overhead to maintain Pipelines if they are set up by individual team members. In this case, team owners can instead create pipelines that are owned by the team rather than an individual.
Adding a new team-shared pipeline
To create a team-shared pipeline, select the plus icon from the Deployment pipelines page, then select Add new team-shared pipeline...
Note: Creating a team-shared pipeline requires you to use team shared org and team shared source control connection - if you don't have them yet then you will need to create them first.
Follow these steps to fully set up your pipeline.
When you create a team shared pipeline, the connection is owned not by you but by the team. This means that it will continue to be available to all team members even if you leave the team in the future.
You can always tell if a pipeline is user owned or team-shared by looking in the list of pipelines.
All team-shared pipelines will appear under the heading TEAM-SHARED
User permissions for team-shared Pipelines
Team shared Pipelines can be edited and managed by any team owner. Team members cannot edit or manage the pipeline, but can run them according to the same rules as user shared pipelines - in other words, based on their permissions to the source and target connections.
Note: If you're a team member and want to convert a user-owned Pipeline into a team-shared Pipeline, this option won't be available to you in Pipelines UI until you're granted a Team Owner status. This is an expected behaviour even if you're the Pipeline owner.
Using team 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.