> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-compose/content-orchestration/collections.md). # Collections Collections are containers for logically grouping related content within an environment, and they define the root scope for GraphQL queries (with optional traversal via references and filters). A collection in Umbraco Compose is a container for logically grouping related content. There may be one or more collections per [environment](/umbraco-compose/content-orchestration/environments.md). The content instances you ingest should be placed into an existing collection of your choice. ## Collection Considerations When designing your content architecture in Umbraco Compose, you should keep in mind some collection principles. Requests to the GraphQL API will always target a single collection for the root content that they return. However, it is also possible to retrieve other content in a single query if it is [referenced](/umbraco-compose/content-orchestration/referenced-content.md) from an item in the target collection. GraphQL queries will return all items in the target collection unless they are explicitly [filtered out](/umbraco-compose/apis/graphql/filtering.md). --- # 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.umbraco.com/umbraco-compose/content-orchestration/collections.md?ask=&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.