> 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/account-management/organization-management/organization-settings/create-an-organization-collaboration.md). # Create An Organization Collaboration Connect two organizations so you can share selected nests. An organization collaboration connects your organization with another organization. It lets either organization share selected nests with the other. The collaboration doesn't grant access to every nest. Use a collaboration when you need to share a nest with an organization you don't belong to. Without one, you can add only your own organizations to a nest. {% hint style="warning" %} Create a collaboration to share a nest's **AutoLit** workflow with another organization. You don't need one to share **Synthesis**. See [Sharing and Access](/collaborate/sharing-and-access.md). {% endhint %} ## Before You Start An **Owner** or **Admin** creates the invitation then sends it to an admin of the other organization. The invitation link works once and expires after seven days. It can only be accepted by a single organization so a new link should be generated for each organization collaboration. Creating a collaboration doesn't give the other organization access to any nests. {% stepper %} {% step %} ### Send A Collaboration Invitation In **Organization Management**, select **Organization Details**. Under **Collaborations**, select **Invite Collaborator**.
The Collaborations section in Organization Details with the Invite Collaborator button.

Create an invitation from the Collaborations section.

Copy the one-time invitation link and send it to the other organization's admin.
A collaboration invitation dialog showing a one-time invitation link and copy control.

Copy the one-time invitation link.

Return to **Collaborations** anytime to copy the link again or delete it. {% endstep %} {% step %} ### Accept The Invitation The recipient opens the link, selects the organization they represent, then selects **Accept**.
The Accept Collaboration Invitation page with an organization selector and Accept button.

Select the organization that accepts the invitation.

The collaboration appears in **Organization Details** for both organizations.
The Collaborations section showing an active collaboration with another organization.

An active collaboration appears for both organizations.

{% endstep %} {% step %} ### Share A Selected Nest After the collaboration is active, either organization can add the other to a nest. In the nest's **Settings → Access**, add the collaborator organization and choose the access you want to grant. For the complete access and ownership options, see [add an Organization to a nest](/collaborate/sharing-and-access.md). {% endstep %} {% endstepper %} ### Removing A Collaboration If you wish to remove an existing organization collaboration, under **Collaborations** select the trash icon next to the organization title. This removes ability of either organization to grant access to future nests but does not remove access to already granted nests. --- # 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/account-management/organization-management/organization-settings/create-an-organization-collaboration.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.