# Collections A **Collection** is where content in Amondo's back-end is organised and managed. Every piece of content, whether created or sourced, is stored inside a Collection before it can be displayed in an Imprint. Collections act as the central workspace where teams can review, manage and prepare content for publishing. ### Purpose of Collections Collections serve three main purposes: 1. **Storage** – they hold all content items that a team has created or imported. 2. **Organisation** – they provide a structured way to manage content, making it easier to curate and prepare for publishing. 3. **Connection** – they can be linked to one or more Imprints, allowing the same content to be reused across multiple experiences. ### Working with Collections * Each Collection has its own name and appears in the Collections list for users with access. * Collections can be connected to one or more Imprints, meaning content can be published in different formats without duplication. * Collections can be created for different campaigns, projects or teams to keep content separate and manageable. ### Collections and Imprints Imprints are the layouts or formats used to display content. Collections provide the source content that Imprints draw from. By connecting a Collection to an Imprint, you make its content available for use in galleries, carousels, stories or displays. ### Related * [Imprints](/getting-started/core-platform-concepts/imprints-and-formats.md) * [Tiles](/getting-started/core-platform-concepts/tiles.md) --- # Agent Instructions: 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: ``` GET https://docs.amondo.com/getting-started/core-platform-concepts/collections.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.