> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-projects/project-collections-groupings.md).

# Project collections groupings

How to group Projects using collections and views

{% hint style="info" %}
**Feature availability**\
This feature is available only with Enterprise Plans. For more information, see [plans and pricing](https://snyk.io/plans/).
{% endhint %}

There are two ways to group your Projects: **Project views** and **Project collections**.

**Project views** are flexible collections you can create based on the filters available on the Project listing page.

In the Snyk Web UI, you can:

* Create and configure a dynamic Project view that is based on filters
* Share links to views of the Project listing page that you use with another member of your Organization
* View reports on your Project views

{% hint style="info" %}
Any Organization-level role can create and share Project views.

You can create and configure a Project view only when you apply the **Group by none** grouping in the Project listing page.

In addition, more filter options are available when you apply **Group by none**.

Views are visible to and can be edited by anyone in your Organization.
{% endhint %}

For details, see the [Project views](/scan-fix-and-prevent/scan-with-snyk/snyk-projects/project-collections-groupings/project-views.md) page.

**Project collections** help you collect and organize your Projects so you can easily view and perform actions on them.

Project collections are static collections of Projects which can be built using a combination of filters and selecting individual Projects. A Project collection can consist of multiple Project types from different Targets.

Project collections live on the Organization level, which means they are available for all members of the Organization to view and work within.

{% hint style="info" %}
Project views can be created by any user in an Organization, while Project collections can be created by users with admin roles and custom roles with the appropriate permissions. The permissions that a custom role requires to be able to use collections are:

* Read
* Create
* Delete
* Edit

For more information, see [Pre-defined roles](https://docs.snyk.io/platform-administration/user-management/pre-defined-roles).
{% endhint %}

In the Snyk Web UI and [API](https://docs.snyk.io/developer-tools/snyk-api/reference/collection), you can:

* Create collections using filters and selecting Projects individually
* View all of the collections that have been created on a collections listing page
* Perform bulk actions such as deleting, deactivating, and activating Projects in a collection. Performing bulk actions is not exclusive to collections, and can be done on Projects in the Project listing page.

For details, see the [Project collections](/scan-fix-and-prevent/scan-with-snyk/snyk-projects/project-collections-groupings/project-collections.md) page.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-projects/project-collections-groupings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.