> 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/accepting-invites.md).

# Accepting Invites

Join an Organization or access a shared nest from an invitation.

An invitation gives you access to a nest or an **Organization**. Accept it to collaborate with the people who shared it.

The steps differ if you need to create a Nested Knowledge account first.

### Create An Account Before Accepting An Invite

If you don't have a Nested Knowledge account, select the link in the invitation email. Create your account, verify your email address and sign in.

{% hint style="info" %}
Unable to find the link? [**Create an account here.**](https://nested-knowledge.com/sign-up)
{% endhint %}

### Accept A Nest Invite

After you sign in, accept the invitation on the [**Nests page**](/your-nests/nests.md)**.** It will automatically open the nest.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2Fe7kjQQO5K7Ox8qIE8klS%2Fnest%20invites.png?alt=media&amp;token=0c7fddc1-b0b9-49e4-8208-95f152d63e42" alt="A pending nest invitation on the Nests page."><figcaption><p>Accept a pending nest invitation from the <strong>Nests</strong> page.</p></figcaption></figure>

### Accept An Organization Invite

An Organization gives you access to every nest it can reach.

1. Open the invitation email and select its link. Alternatively, navigate to the [**Organizations** page](https://nested-knowledge.com/manage/organization).
2. Select the check mark beside the pending invitation.
3. If you have been granted admin access, select the **Organization** to view its details.

You can also open the **Organizations** page from the user menu.

<figure><img src="https://content.gitbook.com/content/xb7uNGATUgwQAjDVQRXG/blobs/iMLu4QFItyCAVzeu3c8Z/AD_4nXfSprPbGDZHVg3ltQFehBkt_HLjEDWCPfwhNPMgATyjC1%20yo2JcOoEwum9RDcsASynwTkfHj_Uc_2e4Xkrm645CeBw675zG1n8r1AFZ57vra4W%20E8btJsacCCwS2yEplR3LYjuM" alt="A pending organization invitation with a check mark to accept it."><figcaption><p>Select the check mark to accept a pending organization invitation.</p></figcaption></figure>

{% hint style="info" %}
Don't see any pending organization invites? Ensure your admin has sent you an invite.
{% endhint %}

### See Also

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-share-nodes">:share-nodes:</i><br><strong>Sharing and Access</strong></td><td>Share a nest with people and organizations.</td><td><a href="/collaborate/sharing-and-access.md">Sharing and Access</a></td></tr><tr><td><i class="fa-user-plus">:user-plus:</i><br><strong>Invite Members to Your Organization</strong></td><td>Add people who need access to every nest in your organization.</td><td><a href="/collaborate/invite-your-team.md">Invite Your Team</a></td></tr><tr><td><i class="fa-users">:users:</i><br><strong>Member Management</strong></td><td>Manage organization members and their access levels.</td><td><a href="/collaborate/member-management.md">Member Management</a></td></tr></tbody></table>


---

# 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/accepting-invites.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.
