Pipelines are a powerful tool to help your teams manage where changes are in your release workflow. Large teams or organisations might struggle to view only the developer sandboxes that are relevant to them.
In cases like this, you can assign a sandbox to a member of your team and configure your pipeline to show only the sandboxes that are assigned to a specific team member.
Assign existing sandboxes to a team member
Step 1: Choose your sandbox
In the pipelines view select the sandbox (by clicking on it) that you want to assign to a team member.
Step 2: Assign a developer sandbox to a team member
On the three dots select Assign to team member... (screenshot above), then select the team member from the dropdown list and click Save:
The sandbox will now show the initials of the user it's assigned to:
Note: Once you have assigned a sandbox it can be re-assigned by clicking on Re-assign to team member... from the three dots.
Assign to a team member when creating a new sandbox
During the Add new developer sandbox environment flow you'll see an option Assign to team member. From this dropdown you can select the team member to whom the sandbox can be assigned.
Change pipeline visibility settings
With developer sandboxes now assigned to team members you can configure the pipeline visibility settings.
Step 1: Edit pipeline details
Select the gear icon for your pipeline settings (on the top left) and click Edit pipeline details...
Step 2: Change developer sandbox visibility
On the Developer sandbox visibility option, select Team members cannot view other users' assigned sandboxes and click Save.
Team owners can view all developer sandboxes within the Pipeline setup, but after the above setting is configured team members will only be able to view those sandboxes assigned to themselves, or those that are currently unassigned.