> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rocket.new/llms.txt
> Use this file to discover all available pages before exploring further.
# Task visibility
> Toggle Rocket.new Build tasks between public and private to control who can view your app, see work-in-progress builds, or open the task link.
export const LlmsDirective = () =>
For the complete documentation index, see llms.txt.
For a lightweight markdown version of this page, append .md to the URL.
;
Every **Build** task has its own visibility setting. You choose who can view each Build task: just you and people with access, or anyone with the link. Visibility is set per Build task—not per project—and does not apply to Solve or Intelligence tasks.
## Visibility levels
| Level | Who can see it | Best for |
| :---------- | :------------------------- | :--------------------------------------------------------- |
| **Public** | Anyone with the link | Showcasing work, sharing examples, community contributions |
| **Private** | You and people with access | Personal work, sensitive data, draft explorations |
Public Build tasks display a "Built with Rocket" badge (also called the Rocket watermark). Anyone with the link can view the output. Anonymous viewers stay view-only—only the task owner and people with edit access can chat and iterate. Private Build tasks are hidden from people who do not have access, even if they have the URL.
Setting a Build task to Private requires a paid plan (Pro or above). Free plan Build tasks are always Public.
## Set task visibility
You can set visibility when creating a Build task, or change it at any time from inside the task.
Before submitting a new Build task from **Home**, click the **lock icon** next to the send button to choose **Public** or **Private**.
Open the Build task, then click the **task name** at the top-left to open the dropdown.
Select **Settings** from the dropdown.
In the **Overview** panel, open the **Task Visibility** dropdown and choose **Public** or **Private**. The change takes effect immediately.
## How visibility affects sharing
**Public Build tasks:** Copy the task URL and share it with anyone. Recipients can view the task output without logging in.
**Private Build tasks:** Private tasks are hidden from people who do not have access. If you later change a private task to public, the full task history becomes visible immediately.
Changing visibility from Private to Public exposes the entire task history, including all messages and outputs. Review your task content before making it visible.
## Frequently asked questions
Yes. See the steps in the **From inside the task** tab above.
No. Public/Private visibility is a Build-only setting. For Solve report outputs, use [report share links](/solve/results/share-and-export).
No. Visibility controls who can see the task, not what Rocket can do with it. Rocket has full access to the task's files, context, and connected services regardless of visibility.
Existing public links stop working immediately. Anyone who previously opened the public URL will see an error page. If you switch back to public, the same link becomes active again.
No. Each Build task has its own visibility setting. You can have a mix of public and private Build tasks within a single [project](/getting-started/project/overview).
## What's next?
Rename, star, move, or delete a task.
Let others clone a Build task into their own workspace.