License requirements to use team-shared Pipelines:
This feature is available for all customers using Deployment Teams and Automation Starter licenses, or any higher-tier license.
Check our Pricing page for more information about different types of licenses.
On larger teams, where members may be joining and leaving regularly, maintaining pipelines can cause administrative overhead 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, navigate to Deployment pipelines page, and from the dropdown menu select Create new pipeline.
Then our Pipeline Setup Wizard will lead you through the steps of adding a new team-shared pipeline.
Note: Creating a team-shared pipeline requires you to use a team-shared org and a team-shared source control connection. If you don't have them, you'll need to create them first.
Developer sandbox connections do not need to be team-shared, but will need to have access delegated in order to be added to the Pipeline. You can learn how to delegate access to orgs here.
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.
Note: If the banner shown in the screenshot below appears during pipeline creation, it's typically because the VCS provider does not automatically grant the team-shared account read/write access to repositories created in that location. As a result, any future repositories created in the same location will encounter the same issue.
To resolve this, grant the team-shared account read/write permissions. You can also configure your VCS provider to automatically assign these permissions to repositories created in that location, preventing the issue from recurring.
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 - that is, 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 the "Pipelines UI" until you're granted Team Owner status. This is expected behavior 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