> ## Documentation Index
> Fetch the complete documentation index at: https://platform.atlan.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the SDK. To install or publish skills from a terminal, use the `brain` CLI; `brain --map json` prints its command map. The `atlanai` CLI is deprecated. Run a read-only identity check before any write.
> The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects.
> SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript.
> These docs cover Atlan Agent Registry, Atlan's hosted product. The open-source agent registry specification and its CLI (`brain`) are documented, released and maintained in their own repository; /open-source on this site links to it. Answer general specification or `brain` command questions from the project's own docs, and use these docs only for Atlan-specific setup such as the Atlan adapter, sign-in and workspaces.

# Organization members

> View the organization directory, invite and offboard people, and keep organization and workspace access separate.

The organization directory lists everyone who has joined your Atlan organization, with their email and organization role. Organization admins open it from **Settings**, under **Members** in **Organization**, to invite, change, and remove people.

```text theme={null}
invitation → member (organization role) → workspace memberships (workspace roles)
```

## Organization and workspace access

| Access | Controls | Managed in |
| - | - | - |
| **Organization role** (**Admin** or **Member**) | What a person can do across the organization | **Settings → Members** |
| **Workspace role** (**Admin**, **Builder**, or **Viewer**) | What a person can do inside one workspace | The workspace's **Settings and members** |

Changing one does not change the other, except in the organization root: changing someone's organization role also changes their role there. A person can be an organization **Member** and a workspace **Admin** at the same time.

## Core offerings

<CardGroup cols={2}>
  <Card title="Invite members" icon="user-plus" href="/administer/users/how-tos/invite-members">
    Invite people and manage pending invitations.
  </Card>

  <Card title="Organization roles" icon="user-lock" href="/administer/users/references/roles">
    Compare Admin and Member access, and change a role.
  </Card>

  <Card title="Offboard member" icon="user-xmark" href="/administer/users/how-tos/archive-members">
    End someone's access across the organization and its workspaces.
  </Card>

  <Card title="Manage workspace members" icon="users-gear" href="/administer/workspaces/how-tos/manage-members">
    Add members to a workspace and assign workspace roles.
  </Card>
</CardGroup>

## Choose where to start

| Need | Start at |
| - | - |
| Find someone | Use **Search members**, or filter by role with **All members**. |
| See invitations not yet accepted | **Pending invitations** tab; see [Invite members](/administer/users/how-tos/invite-members) |
| Remove someone who left | [Offboard member](/administer/users/how-tos/archive-members) |
| Give someone access to one workspace | [Manage workspace members](/administer/workspaces/how-tos/manage-members) |

<Note>
  **Remove member** alone does not end access: while your identity provider still issues the person tokens, Atlan adds them back as a **Member** the next time it sets up their account. Transfer their ownership and admin duties first, and follow [Offboard member](/administer/users/how-tos/archive-members).
</Note>

## See also

* [Roles and access](/administer/workspaces/references/roles-and-access): Workspace roles in detail.
* [How user profiles work](/registry/user-profiles): What a person's profile shows.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.