> For the complete documentation index, see [llms.txt](https://bluebricks.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluebricks.co/docs/orchestration/collections/create-an-environment.md).

# Creating Collections

## Overview

Collections organize infrastructure into clear units that match how teams actually work. You can create separate collections for projects, teams, or lifecycle stages such as development, staging, and production. Each collection provides the foundation for environments by holding shared settings and rules.

<figure><img src="/files/bVLwXtpXN7P4y2L8VBVY" alt=""><figcaption><p>Example of creating a collection with AWS</p></figcaption></figure>

## How to create a collection via the Bluebricks app

1. Go to the [Collections](https://app.bluebricks.co/collections) page
2. Click **Create Collection**
3. Enter a **name** for the collection
4. Select the **cloud provider(s)** to connect
   1. Haven't connected your cloud accounts yet? [Learn how to connect your cloud](/docs/getting-started/connect-your-cloud.md)
5. Configure any required **settings, permissions, and secrets**
6. Click **Create** to finalize the setup

## How to create a collection via the CLI

You can create a new collection using the Bricks CLI (refer to [Bricks CLI Installation Guide](/docs/bricks-cli/bricks-cli.md) if you haven't installed it yet):

```bash
bricks collection create --name "Self-Hosted Orchestrator"
```

A successful creation displays a confirmation message with the new collection ID:

```
✓ `Self-Hosted Orchestrator` collection created successfully with ID: 42c9d5cf-cf9c-4783-ac1d-4d34140b9299
```

To set the new collection as the default target for commands that don't specify `--collection`:

```bash
bricks collection create --name "development" --default
```

### Naming conventions

* Use clear, descriptive names: `production`, `staging`, `development`
* Include team or project context when needed: `team-alpha-production`
* Follow a consistent pattern across your organization: `{project}-{stage}`

{% hint style="info" %}
After creating a collection, connect a cloud account before deploying. See [Connect your Cloud](/docs/getting-started/connect-your-cloud.md). To manage existing collections (list, enable, disable, delete), see [Managing Collections](/docs/orchestration/collections/managing-collections.md).
{% endhint %}