> For the complete documentation index, see [llms.txt](https://docs.i3d.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.i3d.net/organizations/inviting-a-member.md).

# Inviting a member

Use this when you want to give someone access to your organization **without** touching their own account or resources — a colleague joining your team, a contractor working on one project, or a QA engineer who needs to see a production team's servers.

## To send an invitation

{% stepper %}
{% step %}

#### Open the Members page

Go to **Organization Management → Members**.
{% endstep %}

{% step %}

#### Start the invitation

Click **Invite Member** (top right).
{% endstep %}

{% step %}

#### Enter the email address

Enter the person's **email address**.
{% endstep %}

{% step %}

#### Choose where they join

Choose the **destination organization** — the point in your structure where they should join. Your top-level organization is selected by default; pick an organizational unit to limit them to that unit and everything beneath it.
{% endstep %}

{% step %}

#### Send it

Click **Send Invitation**.
{% endstep %}
{% endstepper %}

The invitation appears on the **Invitations** tab with the **Standard** membership label, and the recipient gets an email.

## What the invitee gets

* Access to the organization you invited them to, and everything beneath it.
* Nothing changes for their own account: their existing organization, account number and servers stay exactly where they are and stay theirs.

The dialog states this on screen so there's no doubt:

> This invitation will be sent as **member-only** — the invitee gains access to your organization without their existing account being consolidated.

{% hint style="info" %}
If you meant to consolidate an account instead, use **Organization Management → Import organization**. See [Importing an organization](/organizations/importing-an-organization.md).
{% endhint %}

## Messages you might see

| Message                                                                                                | What to do                                                                                  |
| ------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------- |
| *This invitee already inherits membership from a parent organization, so no new invitation is needed.* | They can already reach this organizational unit through a level above it. No action needed. |
| *This email address is already a member of this organization.*                                         | Check the [Members](/organizations/members.md) tab.                                         |
| *An invitation is already pending for this email and organization.*                                    | Look on the Invitations tab — resend it rather than creating a second one.                  |
| *A merge invitation already exists for this email and organization…*                                   | Withdraw the pending **Import Organization** invitation first.                              |
| *You're sending invitations too quickly. Try again in a moment.*                                       | Wait a few seconds and retry.                                                               |

## Related topics

* [Members](/organizations/members.md)
* [Accepting an invitation](/organizations/accepting-an-invitation.md)
* [Importing an organization](/organizations/importing-an-organization.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.i3d.net/organizations/inviting-a-member.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.