<aside>
The third tab under your Project Settings allows you to set up a ready-to-use pool of Scratch Orgs or Sandboxes for your team to use.
</aside>
<aside>
To set up Org Pooling, you’ll need to access your project’s Pool settings.
</aside>
<aside>
<aside>
</aside>
<aside>
<aside>
</aside>
<aside>
You’ll see a different set of options depending on whether your project is a Scratch Org project or a Sandbox project.
</aside>
<aside>
If you’re working with a Scratch Org project, you’ll see the following options:
</aside>
<aside>
</aside>
<aside>
Here, you have the option to specify a Scratch Org Snapshot to create your Pool Orgs from. If you don’t select one, your Pool Orgs will be created and refreshed from your main branch.
</aside>
<aside>
This email address is where all information about your Scratch Orgs will be sent, such as error messages. You can easily change this to a different email address - just type a new one in and click “Save” down at the bottom of the window.
</aside>
<aside>
This is the default length of time (in days) that your Scratch Orgs will exist before they expire.
</aside>
<aside>
This is the number of Scratch Orgs that will be in your Pool.
</aside>
<aside> <img src="/icons/flash_yellow.svg" alt="/icons/flash_yellow.svg" width="40px" /> Increasing this number will automatically start spinning up the specified number of Scratch Orgs into your project’s Org Pool.
</aside>
<aside>
We recommend to set this to the approximate number of Scratch Orgs that your team will use concurrently. Two Pool orgs for each of your team members is a good rule of thumb, but you can always set this to more or fewer depending on the needs of your team.
</aside>
<aside>
If you’re working with a Sandbox project, you’ll see the following options:
</aside>
<aside>
</aside>