> 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/user-area.md).

# User Area

User Area is your personal workspace inside Patcher.

It brings your saved modules, racks, patches, manuals, and profile controls together.

User Area is only available to signed-in users.

![User Area on iPad Pro](/files/kBetdFcHibuneIAkJELd)

## What is in User Area

The layout is built around a few practical sections:

* **Modules** you have added to your collection
* **Racks** you are planning or maintaining
* **Patches** you are documenting
* **Profile stats** and **contributor stats**
* **Manuals** gathered from your saved modules
* **Comments** you have left around the platform
* a floating **global search** field for workspace-wide filtering

The sections are paginated when they grow large, so you can move through bigger workspaces without one long scroll.

## Why it matters

This is where Patcher shifts from public catalogue to working tool.

As your workspace grows, User Area becomes the fastest way to:

* find your own data again
* see what is missing
* jump back into an unfinished idea
* open manuals without leaving the app

## Global search

The search field is not tied to a single section, but it is not one combined result list either.

Instead, the same query is applied across the main sections at the same time:

* **Modules** search name, manufacturer, description, and tags
* **Racks** search name and description
* **Patches** search name, description, and tags
* **Manuals** search module name, manufacturer, and description
* **Comments** search comment text and author usernames

The **Patches** section also has its own tag filter, which works alongside the main search field.

## Profile controls

User Area is also where you control whether your public profile is visible.

From here you can:

* make your profile public or private
* open your public profile
* copy your public profile link

For public discovery, both the profile and the individual rack or patch need to be public.

## A good first setup

1. Add the modules you own.
2. Create one rack.
3. Create one patch.
4. Check that your profile settings match what you actually want public.

That is usually enough to make the workspace start paying off.

## Related pages

* [Collection](/core-workflows/collection.md)
* [Racks](/core-workflows/racks.md)
* [Patches](/core-workflows/patches.md)
* [Public Profiles](/core-workflows/public-profiles.md)
* [Account and Privacy](/core-workflows/account-and-privacy.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/user-area.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.