> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/collaborate/sharing-and-access.md). # Sharing and Access Learn how to share your nest with internal and external users. Sharing gives other people access to your work—either the collaborative workspace, **AutoLit**, or the published outputs, **Synthesis**. You can add people to a single nest or add them to your Organization. Organization access flows to every nest the Organization can reach. This page is written for the person granting access—a nest's Owner or Admin, or an Organization's Owner or Admin. It covers sharing at the nest level. To add someone to your Organization so they inherit access across nests, see [Invite your Team](/collaborate/invite-your-team.md). To understand how inherited access works, see [Permissions and inheritance](/collaborate/member-management/permissions-and-inheritance.md). {% hint style="warning" %} Collaboration isn't available on the free tier, so anyone you add needs a license or an active pilot, and you can't add an Organization to a nest that isn't subscribed. {% endhint %} ### Choosing How To Share Choose the approach that matches the scope of access you need. {% hint style="info" %} **For one nest:** Add an individual or an Organization to that nest. **For every nest your Organization can reach:** [Invite members to your organization](/collaborate/invite-your-team.md). {% endhint %} If a nest is owned by your Organization, every Organization member already has access to it. You don't need to invite them individually. Each member's Organization role determines their nest role. See [Permissions and inheritance](/collaborate/member-management/permissions-and-inheritance.md) and [Roles.](/collaborate/member-management/roles.md) ### Where Sharing Happens Nest-level sharing happens in the nest's **Settings**, under **Access**. Only the nest's Owner and Admins can open this panel. Choose **User** or **Organization,** then **AutoLit** or **Synthesis**. **AutoLit** access lets someone work in the nest and requires an access level. **Synthesis** access lets someone view and share outputs without an access level.

The Access settings panel with User and Organization sharing options, plus AutoLit and Synthesis access choices. — Choose who receives access and whether they can use **AutoLit** or view **Synthesis**.

### Share Access {% tabs %} {% tab title="Add An Individual" %} #### Add An Individual To A Nest In **Settings → Access**, toggle **User**. Then select **AutoLit** or **Synthesis**. Select **Invite Users**, enter the person's email, choose their access level, and send the invitation. You can enter several email addresses at once if they will have the same access level, separated by a comma. You can change access levels later. The person receives an email to accept and a link to the nest. Once they accept, their name appears in the User list. The recipient's side of this is covered in [Accepting invites](/account-management/accepting-invites.md). Whether they need a subscription depends on the access you grant. An individual with **AutoLit** access needs one. Someone with **Synthesis**-only access to a public nest does not. See [Roles](/collaborate/member-management/roles.md) for what the Admin and User access levels allow. Set a nest's visibility in [Nest settings](/your-nests/nest-settings.md).

The Invite Users dialog, showing fields for email addresses and an AutoLit access level. — Invite one or more people and assign their **AutoLit** access level.

{% endtab %} {% tab title="Add An Organization" %} #### Add An Organization To A Nest You can add an Organization to a nest only if you're a member of that Organization. To share with an Organization you don't belong to, set up an [Organization collaboration](/account-management/organization-management/organization-settings/create-an-organization-collaboration.md) instead. In **Settings → Access**, toggle **Organization**. Then select **AutoLit** or **Synthesis**. Select **Add organization**, then choose your Organization from the dropdown. If it isn't listed, confirm that you accepted your Organization invitation. Otherwise, ask an Organization Admin to add you. What happens next depends on the **Nest Owner** column: * Leave it blank to grant **access**. Every Organization member receives user-level nest access. This bulk-sharing option gives no elevated privileges, regardless of a member's Organization role. * Select **Owner** to make the Organization the nest's owner. Only one Organization can own a nest. Ownership changes inherited roles: Organization Owners and Admins become nest Admins. See [Permissions and inheritance](/collaborate/member-management/permissions-and-inheritance.md). When an Organization owns a nest, its [Organizational Templates](/account-management/organization-management/organization-settings/organizational-templates.md) populate into the nest. A public nest's **Synthesis** is already viewable by anyone with the link. Set a nest's visibility in [Nest settings](/your-nests/nest-settings.md).

The Organization sharing panel with an organization selector and Nest Owner option. — Add an Organization to grant access or make it the nest owner.

{% endtab %} {% endtabs %} ### Changing Or Removing Access You can change an individual's access level or remove a collaborator from a nest in **Settings → Access** at any time. Reassigning nest ownership to another collaborator demotes you to Admin. Only the new Owner can reverse this change. [Manage or remove members](/collaborate/member-management/manage-or-remove-members.md) explains how to remove someone from an Organization. This revokes their access to, and ownership of, the Organization's nests. ### Nest Synthesis Visibility **Synthesis** is private by default. Only invited collaborators and members of Organizations with nest access can view it. Change its visibility in [Nest Settings](/your-nests/nest-settings.md). Choose one of these visibility levels: * **Private** — Only invited collaborators and members of Organizations with nest access can view **Synthesis**. * **Protected** — Anyone with the link can view **Synthesis**. * **Public** — Anyone can search for and view **Synthesis**. {% hint style="info" %} Sharing a protected or public **Synthesis** link doesn't grant access to **AutoLit**. {% endhint %} ### See Also


Invite Members To Your Organization	Add people who need access to every nest in your organization.	Invite Your Team
Roles	Understand organization and nest role permissions.	Roles
Permissions And Inheritance	Understand how organization access applies to nests.	Permissions and Inheritance
Accepting Invites	Accept an invitation to join an organization or nest.	Accepting Invites
Nest Settings	Manage nest-wide settings, access, and lifecycle actions.	Nest Settings

--- # 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.nested-knowledge.com/collaborate/sharing-and-access.md?ask=&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.