> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/user-guide/core-concept/sharing-your-app/creating-a-public-page.md).

# Creating a Public Page

Sharing the page publicly will allow anyone on the internet having it's URL to view and use the page without logging in.

To create a public page, follow the steps below:

1. Click on the `Add Team` button.
2. Create a **New Team** and name it to **Public team.** 
3. Set specific page permissions (edit or view) for the team. 
4. Click on the `Save Team` button.
5. Go to the page you need to share publicly.
6. Click the `Share` button on the top right. 
7. Go to the **Public Share** tab.
8. Generate the **Public Access link.**
9. Change the team and set it to the created one.
10. Copy and share the invite link with the users you need to share this page.

{% @arcade/embed flowId="J3TAqBQPbdroSMpuLjzF" url="<https://app.arcade.software/share/J3TAqBQPbdroSMpuLjzF>" %}


---

# 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://docs.jetadmin.io/user-guide/core-concept/sharing-your-app/creating-a-public-page.md?ask=<question>&goal=<endgoal>
```

`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.