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

# Members

Go to **Organization Management → Members**. The page has two tabs: **Members**, and **Invitations** (admins only).

## Members tab

Search by email at the top right. Sort by clicking the **Email** or **Role** heading.

| Column         | What it shows                                                             |
| -------------- | ------------------------------------------------------------------------- |
| **Email**      | The member's email address, with an initials avatar.                      |
| **Role**       | **Admin** if they can administer this organization, otherwise **Member**. |
| **Membership** | How they relate to this organization — see below.                         |
| **Actions**    | The ⋮ menu (admins, and anyone permitted to unmerge).                     |

### Membership labels

* **Owner** — the member who originally created this organization.
* **Core** — someone who created an organization that has since been merged into this one.
* **Standard** — a member with access to this organization's resources.

Hover any label for the same explanation in the Console.

## Actions on a member

| Action              | What it does                                                                                          |
| ------------------- | ----------------------------------------------------------------------------------------------------- |
| **Assign as Admin** | Grants admin access immediately. Shown only for a member who isn't already an admin.                  |
| **Reset MFA**       | Clears the member's MFA enrolment so they can register a new device. Shown only when MFA is enforced. |
| **Remove Member**   | Removes access immediately. Cannot be undone.                                                         |

Some members can't be removed:

* The **Owner** of the organization.
* **Core** members — their organization was merged into yours, so removing them would strand it. [Unmerge it](/organizations/importing-an-organization.md#reversing-an-import) instead.

## Invitations tab

Shows invitations that are still waiting to be accepted.

| Column         | What it shows                                                                                                                                                                                         |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Email**      | Who it was sent to.                                                                                                                                                                                   |
| **Invited by** | Who sent it.                                                                                                                                                                                          |
| **Membership** | The membership the invitation will produce once it's accepted — **Standard** for an ordinary invitation, **Core** for an *Import organization* one. Hover it for the same explanation in the Console. |
| **Sent**       | How long ago it was sent (for example *Today*). Hover for the exact date and time.                                                                                                                    |
| **Expires**    | How long is left (for example *In 3 days*). Overdue entries appear in red.                                                                                                                            |
| **Actions**    | The ⋮ menu.                                                                                                                                                                                           |

{% hint style="info" %}
The **Membership** column is how you tell the two kinds of invitation apart. A **Core** row is an *Import organization* request, which consolidates the invitee's account into yours. A **Standard** row is an ordinary member invitation, which doesn't touch their account. See [Inviting a member](/organizations/inviting-a-member.md) and [Importing an organization](/organizations/importing-an-organization.md).
{% endhint %}

From the ⋮ menu you can:

* **Resend Invitation** — sends a fresh email with a new link and a new expiry. The previous link stops working.
* **Delete Invitation** — withdraws it. The recipient can no longer join with that link.

{% hint style="info" %}
Once an invitation is accepted, expires or is withdrawn, it drops off this list. An empty list means there is nobody you're waiting on.
{% endhint %}

## Related topics

* [Inviting a member](/organizations/inviting-a-member.md)
* [Importing an organization](/organizations/importing-an-organization.md)
* [Organization overview and settings](/organizations/overview-and-settings.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/members.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.