> For the complete documentation index, see [llms.txt](https://docs.flxbl.io/flxbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flxbl.io/flxbl/codev/pools/getting-started.md).

# Getting Started

Pools keep a stock of ready-to-use Salesforce environments — sandboxes cloned from a source org, or scratch orgs created from source — provisioned ahead of time. This guide covers activating the feature and creating your first pool. If any term here is unfamiliar (Dev Hub, SFDX auth URL, GitHub App), the [CI/CD getting started guide](/flxbl/codev/ci-cd/getting-started.md#concepts) explains each one.

## Step 1: Activate the feature

On the **Activate Features** page, open the **Pools** card. Its setup wizard has two steps, both shared with other features:

* **App Integration** — connect GitHub, as in [Step 3 of the CI/CD guide](/flxbl/codev/ci-cd/getting-started.md#step-3-connect-github-app-integration).
* **Dev Hub** — register the Dev Hub org that will provision the pool's environments, as in [Step 4 of the CI/CD guide](/flxbl/codev/ci-cd/getting-started.md#step-4-connect-your-dev-hub).

<figure><img src="/files/qgzsL5VXkvhB20iy73Pu" alt="Activate Features page with the Pools card listing App Integration and Dev Hub steps"><figcaption><p>The Pools card needs App Integration and a Dev Hub — steps already complete if another feature set them up.</p></figcaption></figure>

## Step 2: Create a pool

Under **Pools**, click **Create Pool** and work through the wizard:

1. **Basic info** — pool type (**Sandbox** or **Scratch Org**), a name, a unique tag, the repository, and the Dev Hub. For sandbox pools, optionally a source sandbox to clone from.
2. **Pool config** — minimum available instances (codev provisions more when the pool drops below it), maximum total, how long unassigned environments are kept, and the expiration strategy.
3. **Review** — the generated configuration, editable before saving.

codev starts provisioning immediately and keeps the pool topped up from then on.

<figure><img src="/files/Z6A9YYkV9mqRLUgs4PkD" alt="Create Pool wizard with pool type, name, repository, and Dev Hub fields"><figcaption><p>The Create Pool wizard.</p></figcaption></figure>

## Step 3: Use the pool

The Pools page shows each pool's provisioned, available, and assigned counts. Developers fetch an environment from a pool when they need a fresh org, and [review environments](/flxbl/codev/inspect/review-environments.md) are assigned from pools automatically when pull requests open.

<figure><img src="/files/OdtfgSnlxeAS0UylhZUd" alt="Pools page showing pools with instance counts and availability"><figcaption><p>The Pools page: availability at a glance.</p></figcaption></figure>

## Where to go next

{% content-ref url="/pages/oZmxjGKfWDCoAwy8BFve" %}
[Creating and Configuring Pools](/flxbl/codev/pools/creating-pools.md)
{% endcontent-ref %}

{% content-ref url="/pages/Pa1TYkeFP4tblZZDut0O" %}
[Fetching and Using Environments](/flxbl/codev/pools/using-pools.md)
{% endcontent-ref %}

{% content-ref url="/pages/1fgX5e1zLiKl7hF33997" %}
[Pool Monitoring and Health](/flxbl/codev/pools/monitoring.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flxbl.io/flxbl/codev/pools/getting-started.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.