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

# Collections

Prisma Cloud Collections allow you to define logical groups of assets within Prisma Cloud, in a way that is meaningful to the stakeholders in your cloud environments. You can create Collections to represent applications and services, organize your cloud estate by business units, or maintain focused visibility on the security posture of the critical components of your cloud infrastructure.

## Create a Collection

Follow the steps below to create a Collection:

1. From the Prisma Cloud administrative console select **Settings > Collection > Add Collection**.
2. Enter a name for the Collection in the **Name** field and provide an optional **Description** for reference.
3. Define the scope of the Collection by selecting the Account Groups, Cloud Accounts, and Repositories which contain the assets you wish to include.
4. Select **Next** and **Save** to finalize your changes.

**Manage Collections**

Previously created Collections can be edited, cloned or deleted as needed. Explore the various options as shown below:

<figure><img src="/files/JIqMKyNVr1eYfGGf39cH" alt="manage collections"><figcaption></figcaption></figure>

Next, review how you can use a collection to track key metrics for the assets you wish to monitor, with Prisma Cloud’s [Code to Cloud dashboard](/content-collections/dashboards/dashboards-code-to-cloud.md).

When you create a collection, you can select any repository that is added on **Prisma Cloud on Settings > Code & Build Providers**. If the repository is removed subsequently, the Collection is not automatically updated.


---

# 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.prismacloud.io/content-collections/administration/collections.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.
