> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/administration/sharing-and-privacy.md).

# Sharing and privacy

Control who can see and edit your work.

Everything you create in Zerve, from notebooks and threads to superagents and data connections, has a **privacy setting** and can be shared with specific people.

## Privacy settings

| Setting     | Who can access it                                                                                                  |
| ----------- | ------------------------------------------------------------------------------------------------------------------ |
| **Private** | You, and the people you invite. This is the default.                                                               |
| **Team**    | Every member of the organization can find it, open it and edit it. Available on **Team** and **Enterprise** plans. |
| **Public**  | Anyone with the link can view it, but not edit it                                                                  |

Only the owner can change a resource's privacy setting.

## Sharing with specific people

Invite people with one of two permissions:

| Permission | What they can do |
| ---------- | ---------------- |
| **Read**   | View it          |
| **Write**  | View and edit it |

Lists of shared items also show who the **owner** is.

## How access is worked out

If several things give someone access, the highest level wins. Someone has access to a resource if any of these apply:

* They own it, or own the folder it's in
* They're an Owner or Admin of its organization
* They've been invited to it, or to the folder it's in
* It's set to **Team**, or the folder it's in is, and they're a member of the organization
* The organization's [member permissions](/zerve-docs/administration/members-and-roles.md#member-permissions) give them access to that kind of resource
* It's **Public** (read access only)

### Folders

**Access flows down one level from a folder.** Sharing a folder, or setting it to Team, gives access to the items directly inside it.

**Being invited to something lets you open its folder.** If you're invited to a notebook inside a folder, you can open that folder to view it.

## Sharing with people outside your organization

| Permission | What happens                                                                                                                                                                                                                                                               |
| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Read**   | Anyone can be given read access. It doesn't use a seat.                                                                                                                                                                                                                    |
| **Write**  | Write access requires membership of the organization. When someone outside it accepts a write invitation, they're added to the organization, which uses a seat. **If there are no seats left, they get read access instead**, and the person who invited them is notified. |

If you invite someone who doesn't have a Zerve account yet, the invitation is waiting for them when they sign up.

## Sharing superagents

People with read access to a [superagent](/zerve-docs/superagents/superagents.md) can ask it questions, but they can't start work, set schedules or change anything about it.

## Assets stay in their organization

Assets such as data connections, constants and functions can't be used outside the organization they belong to, even if you can see them. See [Assets overview](/zerve-docs/data-and-assets/data.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zerve.ai/zerve-docs/administration/sharing-and-privacy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.