# Visibility and sharing A lab is either **private** or **public**. There is no middle state. | Visibility | Who can see it | | --- | --- | | Private | You, the owner | | Public | Anyone, signed in or not — discoverable and downloadable from the Hub | ## Changing it Publishing moves a lab's visibility as a side effect of cutting a release. Setting visibility on its own is the other half. It re-scopes a lab you already own **without releasing anything new**, so making something private again doesn't mean inventing a version to do it. - In Studio, from the lab. - From an agent, with `lab_visibility_set` (scope `packages:publish`). See [Agent tool reference](/agents/tools#evidence-and-publishing). Only the owner can change who sees a lab. If you don't own it, fork it into a workspace you do. ## What going public means **Warning:** Public labs can be discovered and downloaded by anyone. Copies already taken stay with whoever took them. Making a lab private again stops new copies. It doesn't recall the ones already taken, and it doesn't delete releases you already published. Those versions are immutable. ## Publishing publicly is always a separate approval You can give an agent a grant covering repeated runs, or runs paired with **private** publication. No grant covers a public release. That approval gets asked for every time, and a workflow grant that requests a public publication is refused outright. See [Approvals and grants](/agents/approvals). ## Sharing without publishing To show someone your work without making a lab public, share a read-only Studio workspace snapshot instead. See [Guest and account mode](/studio/guest-and-account#sharing). ## Next steps - [Package and publish](/hub/publish): cutting a release - [Approvals and grants](/agents/approvals): what a grant covers - [Hub](/hub): what a published release is