Assign sandboxes to your team

If your team has a large number of sandboxes it can be challenging to see only those relevant to you. Sandbox assignment can help.

K
Written by Kenny Vaughan
Updated over a week ago

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 team member.

Assign existing sandboxes to a team member

Step 1: Choose your sandbox

In the pipelines view select the sandbox you want to assign to a team member.

Step 2: Assign a developer sandbox to a team member

On the kebab menu (three dots) select "Assign to team member" 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:

Once you have assigned a sandbox it cannot be re-assigned. If you need to change a sandbox assignment you will need to recreate the sandbox.

Assign to 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 which 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

On the gear icon for your pipeline 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

Owners can view all sandboxes but now team members will only be able to view those assigned to themselves or those that are unassigned.

Did this answer your question?