> 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/public-profiles.md).

# Public Profiles

Public profiles are the shareable face of your workspace.

They give you a clean page tied to your username without making everything you do in Patcher public.

![Public profile on iPad Pro](/files/U0AorSE5HcHw2aNm99bt)

## What a public profile can show

When enabled, a profile can show:

* your username
* your website link, if one is present on the profile
* public racks
* public patches
* profile stats
* contributor stats

## What stays under your control

Public visibility is a choice, not a requirement.

You can keep your profile private and still use the rest of Patcher normally.

Public browsing only shows racks and patches when both the item itself and the profile are public.

## Typical uses

* sharing a curated set of racks
* linking people to selected patches
* giving collaborators or followers one stable page
* building a public presence without exposing your whole workspace

## Useful actions

From your own profile flow, you can usually:

* view your public profile
* copy the public link
* switch the profile between public and private

## Best practices

* make the profile public only when the visible content is intentional
* keep names, descriptions, and links clean before sharing
* treat the profile as a curated public surface, not a dump of everything

## Related pages

* [User Area](/core-workflows/user-area.md)
* [Account and Privacy](/core-workflows/account-and-privacy.md)
* [FAQ](/project/the-project.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/public-profiles.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.