> 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/invite-your-team.md). # Invite Your Team Learn how to invite team members to your organization. ### Invite Members To Your Organization Add people to your Organization when they need access to every nest it can reach. You grant access once at the Organization level, rather than on each nest. To share one nest with someone outside your Organization, use [Sharing and Access](/collaborate/sharing-and-access.md). {% hint style="info" %} The Organization must be set up with an active license or pilot in order to invite members. Only an Organization's Owner and Admins can invite members. {% endhint %} ### Send An Invite {% stepper %} {% step %} #### Open Your Organization Select the user menu in the top right, then select **Organizations**. Select the Organization where you want to add people. To create an Organization, see [Organization Management](/account-management/organization-management.md). {% endstep %} {% step %} #### Start The Invitation Select **Invite Members**.

The Organizations page with the Invite Members button highlighted. — Select **Invite Members** to start an invitation.

{% endstep %} {% step %} #### Enter Details And Send Enter the person's email address. Enter several addresses when everyone receives the same role, separated by a comma. If your Organization is subscribed, a warning is shown indicating the total seats taken and remaining. Choose **Organization Member** or **Organization Admin**, then send the invitation. Both roles can use every nest the Organization reaches. An Admin can also manage the Organization. See [Roles](/collaborate/member-management/roles.md) for role details.

The Invite Members dialog with fields for email addresses and an organization role. — Enter email addresses and select an Organization role before sending the invitation.

{% endstep %} {% endstepper %} ### Pending Invites And Acceptance After you send an invite, the address appears under **Pending Invite**. A check mark shows that the person already has a Nested Knowledge account. The recipient should be prompted to create an account before accepting the Organization invite. They can accept from the email link or their **Organizations** page. They remain under **Pending Invite** until they accept. After acceptance, they appear in the Users list. See [Accepting invites](/account-management/accepting-invites.md) for the recipient's steps. ### Once They've Joined After someone joins, you can change their role or remove them. You can also withdraw an unaccepted invitation. See [Manage or remove members](/collaborate/member-management/manage-or-remove-members.md). ### Grouping Members Create a team when some members need access to a distinct set of nests. A team draws from people already in the Organization. Invite members and wait for their acceptance first. See [Teams](/collaborate/member-management/teams.md). ### See Also


Manage Or Remove Members	Change member roles, remove members, or withdraw pending invites.	Manage Or Remove Members
Roles	Understand organization and nest role permissions.	Roles
Permissions And Inheritance	Understand how organization access applies to nests.	Permissions and Inheritance
Teams	Organize members and nests into focused teams.	Teams
Accepting Invites	Accept an invitation to join an organization or nest.	Accepting Invites
Sharing And Access	Share a nest with people and organizations.	Sharing and Access

--- # 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/invite-your-team.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.