> For the complete documentation index, see [llms.txt](https://docs.patcher.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patcher.xyz/core-workflows/collection.md).

# Collection

Your collection is the foundation of the whole workspace.

If Modules is the catalogue, Collection is the working inventory behind everything else.

Collection management requires a signed-in account. Public visitors can browse modules without logging in, but they cannot save modules into a personal collection.

## What the collection does

The collection tracks the modules you want available in your workspace.

That matters because Patcher uses the collection as the source for:

* rack planning
* patch creation
* manual shortcuts in your user area
* a more accurate picture of your real system

## Build your collection

1. Sign in.
2. Open **Modules**.
3. Find a module you own.
4. Add it to your collection.
5. Repeat until your core system is represented.

You do not need to add everything in one sitting. Start with the hardware you reach for most often.

## Why this step is worth doing well

A strong collection makes everything downstream faster and more believable:

* racks become realistic
* patches are easier to assemble
* public sharing reflects your actual setup
* manuals gather in one place as your library grows

If your collection is incomplete, the rest of the workspace becomes harder to trust.

## Collection is not just storage

Think of it as working data, not passive storage.

A good collection helps you answer questions like:

* what do I actually own?
* what rack variants can I build from it?
* what modules keep appearing in my patches?
* what manuals do I need access to regularly?

## Good habits

* add modules as they arrive
* remove or adjust entries when your system changes
* use the collection before making a new rack or patch
* submit missing modules instead of working around gaps forever

If you see disabled collection actions while browsing publicly, that is expected. Those actions become available after you sign in.

## Where it leads next

Once the collection feels accurate, move on to:

* [User Area](/core-workflows/user-area.md)
* [Racks](/core-workflows/racks.md)
* [Patches](/core-workflows/patches.md)
* [Public Profiles](/core-workflows/public-profiles.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.patcher.xyz/core-workflows/collection.md?ask=<question>
```

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.