License requirements:
This feature is available for all team owners on a Deployment Teams or Deployment Enterprise license.
If you're a team member with a Deployment Teams license, you'll have access to create a team-shared org connection when an existing team owner upgrades your team role from "Member" to "Owner" on Team management page.
For larger teams, team-shared Salesforce org connections give a simple way to share org access and maintain security. For sandbox seeding, team-shared connections can be used as a source or target. If you have access to the connection, they will be listed alongside personal connections, when starting to configure a sandbox seeding.
Security
Team-shared Salesforce org connections can be used as a source or target by all team owners. For team members, access is controlled through roles. Team members can be given Data Access of Read and Write, Read or None through a role.
Read and Write: the connection can be used as a source or target for sandbox seeding. The connection will be usable as a target for in-place masking (coming soon).Read: the connection can be used as a source for sandbox seeding. The connection can't be used for in-place masking.None: the connection can't be used for sandbox seeding or in-place masking.
Disabling Automations
It is advisable that users have Comparison metadata access for the source and Deployment metadata access for the target. This will allow the user to disable automations before the seeding and roll it back after.