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

# Set up your organization

> Set up your e6data organization - invite members, assign roles, and enable domain auto-join.

An **organization** (tenant) is created when the first user signs up; that user becomes its Admin. This page covers adding members to your organization, choosing their roles, and letting people join automatically by email domain. You need the **Invite users** permission (included in the Admin and Manager roles); role management requires **Manage roles**.

Member management lives under **Access Control**, which has tabs for **Users**, **Roles**, **Groups**, and service-account tokens.

## Invite a member

1. Go to **Access Control → Users** and select **Invite**.
2. Enter the person's email address and select **Send Invite**.

The person receives an email with a login link; when they log in and verify their email, they join your organization. New members start with the **Viewer** role - change it with **Manage roles** on their row. (If your email service isn't configured, the member is still granted access - share the login link directly.)

<Info>
  If SSO is enabled, manual invitations are turned off - members are created automatically on first sign-in through your identity provider. See [SSO overview](/platform/sso).
</Info>

## Roles

e6data ships three built-in roles; assign one or more per member:

| Role | Typical use |
| - | - |
| **Admin** | Organization owners - manage everything, including members, roles, and settings |
| **Manager** | Team leads - manage workspaces, invite members, manage groups and service accounts |
| **Viewer** | Read-only access |

Invited members (and those who join via auto-join) start as **Viewer**. See [Roles and permissions](/platform/identity/roles-and-permissions) for the full breakdown.

## Manage pending invitations

A person you've invited who hasn't logged in yet shows status **Invited**. From **Access Control → Users** you can **Resend** the invitation or **Revoke** it. Email invitations expire after **7 days**.

## Block or remove members

**Block** a member to immediately prevent sign-in without deleting their account (unblock later); **Remove** to take away their access. Blocking takes effect on their next request - an active session won't bypass it.

## Domain auto-join

Instead of inviting people individually, let anyone with an email on your company domain join automatically on first sign-in:

1. Open **Settings** (requires the **Manage organization** permission).
2. In the **Auto-Join Domain** card, switch the toggle **on**. The domain is taken from your account - there's nothing to type. Common public domains (such as `gmail.com`) can't be used.

New users with a matching email then join automatically with the **Viewer** role. Auto-join and invitations can be used together. See [Domain auto-join and JIT provisioning](/platform/identity/domain-auto-join-and-jit).

## Organization vs. workspace access

Organization membership (an org-level role of Admin / Manager / Viewer) is what invitations and auto-join control. **Workspace** access - to a specific workspace inside the organization - is managed separately, from that workspace, directly or via groups. See [Users, groups, and service accounts](/platform/identity/users-groups-service-accounts).

## See also

* [Accept invites](/platform/accept-invites)
* [SSO overview](/platform/sso)
* [Roles and permissions](/platform/identity/roles-and-permissions)

## Keep going

<Columns cols={2}>
  <Card title="Choose a deployment model" icon="cloud" href="/platform/deployment-models">
    Serverless or CloudPrem, on AWS or Azure.
  </Card>

  <Card title="Deploy a workspace" icon="rocket" href="/platform/deploy/aws-serverless">
    Step-by-step guides for each cloud and model.
  </Card>
</Columns>


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