> For the complete documentation index, see [llms.txt](https://help.bloomsharing.com/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bloomsharing.com/doc/getting-started-with-bloom/public-or-private-systems.md).
# Public or private systems
## Public or private systems
If your system is configured as a Public system and a user is geographically near the location of the system, the Public system will show up automatically. The user will just need to select your system from the System Selection screen to join your system.
If your program is configured as a Private system, you will need to distribute the Private System Code to potential users. This code allows users to apply for access to your system. The Private System Code is available in the System → Settings menu in the Dashboard. The Private System Code is available in text format or as a QR code.
After users register with the app, they’ll select the option to “Join a Private System” from the System Selection screen. When prompted, they’ll either enter or scan the Private System Code you have provided.
---
# 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, and the optional `goal` query parameter:
```
GET https://help.bloomsharing.com/doc/getting-started-with-bloom/public-or-private-systems.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.