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

# Collections

Collections in PostLab are here to organize your documents. For example, documents can be categorized by client, project, production, season, document type, etc. It depends on how your team is organized to pick a structure that works for you.

## Create a collection

To create a new collection choose `File > New Collection`. Give it a name and select the newly created collection.

## Add documents

Start adding documents by clicking the `Add Document` button.

## Rename a collection

Misspelled a collection? Decided on a different purpose for a collection? No problem, you can rename the collection in two ways. Either right-click the collection from the sidebar and choose `Rename...`, or select a collection and choose the `•••` menu in the top right corner of the details section and rename the collection.

## Export a collection

In addition to exporting individual documents, you can also export the entire contents of a collection. Select a collection and choose `File > Export Collection...` or press the `cmd + E` shortcut. Alternatively, click the `•••` menu in the top right corner of the details section and select `Export...`. PostLab will ask where the export should be saved. After the export is done, at the location there will be a folder with the collection name, and in it are the documents, individually compressed.

## Activity Feed

Each time a new document version is created within the collection, it will appear in the collection's activity feed.


---

# 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.hedge.video/postlab-1/features/collections.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.