# Managing organizations
> Learn how to manage your organization with MotherDuck
An organization is a top-level entity in MotherDuck that lets you perform administrative functions, such as managing users, setting up billing, configuring sharing, and monitoring security. **Enterprise** customers can [link organizations](/docs/key-tasks/managing-organizations/multiple-organizations/) so one login can sign in to each of them and switch between them.

Organizations are helpful for:

- Grouping users together for tracking usage and billing.
- Sharing data with other users of the same organization.

:::note
MotherDuck is available in multiple regions on AWS and Azure. You choose the cloud and region in which to create your organization. Organizations can only exist within a single cloud region. See [Cloud regions](/about-motherduck/cloud-regions/) for the full list of regions, the DuckDB versions each supports, and regional details.
:::

## Creating an organization

If you already have a MotherDuck account, an organization was already created for you by MotherDuck.

If you are a new MotherDuck user, during sign-up you will be prompted to create a new organization. When you create it, choose the cloud (AWS or Azure) and the [cloud region](/about-motherduck/cloud-regions/) it runs in. You can't change the cloud or region afterward.

![create_org](./img/create_org.png)

:::note
If another coworker at your company already has an organization, you can create your own organization to get started with MotherDuck right away, and then ask them to invite you to their organization later (see ["Joining an existing organization"](#joining-an-existing-organization) below).
:::

## Inviting users to your organization

Viewing organization members and their roles requires permission to view members. Every preset role includes this permission by default. You can check whether teammates are in your organization by navigating to the MotherDuck UI → **Settings** → **Members**.

Inviting teammates requires permission to invite members. The Admin preset role includes this permission by default. The organization invite policy can also grant it to Builder and Explorer users. You can invite teammates without a MotherDuck account and existing MotherDuck users.

![members](./img/members.png)

Changing the organization invite policy requires permission to manage the invite policy, which the Admin preset role includes by default. When member invitations are disabled, only users whose roles include permission to invite members can invite new users. You can configure this setting from the organization **Settings** page.

![invite policy](../authenticating-and-connecting-to-motherduck/authenticating-to-motherduck/img/org-invite-policy.png)

:::tip
If your organization has [SSO enabled](/docs/key-tasks/authenticating-and-connecting-to-motherduck/authenticating-to-motherduck/sso-setup/) you can use
[Just-in-Time (JIT) provisioning](/docs/key-tasks/authenticating-and-connecting-to-motherduck/authenticating-to-motherduck/sso-setup/#just-in-time-jit-user-provisioning) enabled, users in your verified domains who authenticate through your identity provider can join the organization on first login without needing an invitation.
:::

## Joining an existing organization

To join your teammates' MotherDuck organization, someone in that organization with permission to invite members must invite you. The Admin preset role includes this permission by default; the invite policy can also grant it to Builder and Explorer users. MotherDuck doesn't offer a sign-up link that adds anyone to an organization.

### Accept an invitation

The invitation is an email with a link to join the organization. It's valid for 30 days. If it expired, ask anyone in the organization who can invite members to resend it.

1. Open the link in the invitation email.
2. Sign in or sign up with the **same email address** the invitation was sent to. MotherDuck matches invitations by email address, not by name or login method.
3. On the **You have pending invites** page, click **Join** next to the organization.
4. If you're new to MotherDuck, add your first and last name and click **Finish setup**. You don't create an organization or choose a plan.

If you click **or create your own organization** instead of **Join**, you end up in a new, separate organization and your teammates can't see your work. If this already happened, see [Fix an account in the wrong organization](#fix-an-account-in-the-wrong-organization).

If the organization uses [SSO](/docs/key-tasks/authenticating-and-connecting-to-motherduck/authenticating-to-motherduck/sso-setup/), clicking **Join** sends you to your identity provider. Sign in there with your work account.

You can also reach your invitations without the email. Sign in to the [MotherDuck UI](https://app.motherduck.com), open the organization menu in the bottom-left corner, and select **View pending invites** (the item shows how many invitations you have).

### Check which organization and email you're signed in with

The organization menu in the bottom-left corner of the MotherDuck UI shows the organization name and region. Click it to see your name, username, and the email address you're signed in with.

To check from SQL, run [`md_user_info()`](/sql-reference/motherduck-sql-reference/md-user-info):

```sql
SELECT org_name, org_id, username, region FROM md_user_info();
```

If the organization or email is wrong, select **Log out** in the organization menu and sign in again with the email address your invitation was sent to.

### Fix an account in the wrong organization

Accounts in the wrong organization usually come from signing up before the invitation arrived, or with a different email address than the one invited.

- **Invitation was sent to a different email address:** the invite page shows **Invalid Invitation**. Ask your teammate to invite the email address you sign in with, or sign in with the invited address.
- **You already have your own MotherDuck organization:** an account belongs to one organization, unless your organizations are [linked](/docs/key-tasks/managing-organizations/multiple-organizations/) on an Enterprise plan. Accepting the invitation shows "Your current account does not support joining multiple organizations." To join, your current user must be deleted first, which permanently deletes its databases. Copy any data you need to keep into the new organization or a local DuckDB file first, then ask an Admin of your current organization to [remove your user](#removing-users) or [contact support](/docs/troubleshooting/support/). Then open the invitation link again.

Each account has one login method. If you signed up with Google, signing in later with a password for the same email address shows **Alternate login required**. Click **Log in with Google** (or the method shown) to reach the same account.

### Reset your password

Password reset applies to accounts that sign in with an email address and password.

1. Go to the [MotherDuck UI](https://app.motherduck.com) and click **Can't log in to your account?** on the login page.
2. Enter your email address and click **Continue**.
3. Open the reset link in the email and choose a new password.

If you sign in with Google or GitHub, reset your password with that provider. If your organization uses SSO, your identity provider manages your password; contact your IT team. You can't change your password from MotherDuck **Settings**.

## Roles

Roles control what a member can do in the MotherDuck platform and which data they can read. MotherDuck provides three preset roles in a concentric hierarchy: **Admin**, **Builder**, and **Explorer**. The first user in an organization is an Admin, and members invited afterward default to Explorer. Creating custom roles requires permission to create custom roles. Assigning roles to members requires a separate permission to assign roles. The Admin preset role includes both permissions by default.

Organizations created before role-based access control keep their access: existing Admins remain Admin, and existing Members become Explorer.

:::note
Managing users and roles, changing plans, and updating billing information require the corresponding platform permissions. The Admin preset role includes these permissions by default.
:::

For the full role model, the capability breakdown, and setup steps, see [Roles and access control](/docs/concepts/security-and-access/roles-and-access-control/) and [Manage roles and access](/docs/key-tasks/managing-organizations/managing-roles/).

## Deprovisioning users

Deprovisioning a user requires permission to deprovision members. Reactivating a user requires a separate permission to reactivate members. The Admin preset role includes both permissions by default. If you need to revoke a user's access without deleting their data, deprovision them from the context menu in the [Users table](https://app.motherduck.com/settings/members). Deprovisioning is a reversible alternative to [removing](#removing-users) a user.

When you deprovision a user:

- They can no longer sign in to MotherDuck.
- Their personal access tokens and short-lived tokens are revoked.
- Their account, databases, and shares are retained.

To restore access later, choose **Reactivate** from the same context menu. The user can sign in again, but previously revoked tokens are not restored — they need to create new tokens.

Two actions are blocked:

- You can't deprovision yourself.
- You can't deprovision the last active user in the organization.

:::note
If your organization uses SCIM provisioning, user lifecycle is managed by your identity provider and the deprovision and reactivate actions are hidden from the Users table.
:::

## Removing users

Removing a member requires permission to remove members, which the Admin preset role includes by default. If a user leaves your team or no longer needs access, remove them from the organization to restrict data access or clean up resources that are no longer used. This is done from the context menu in the [Users table](https://app.motherduck.com/settings/members).

:::warning
Because a user can only belong to one organization, removing them from the organization permanently deletes the user and all of their data. This action cannot be undone. To revoke access reversibly instead, [deprovision](#deprovisioning-users) the user.
:::

## Deleting your organization

MotherDuck has no separate action for deleting an organization. An organization is deleted when its last member deletes their own account.

:::warning
Deleting the last account permanently deletes the organization and all of its databases and shares. This action cannot be undone. Before you delete the account, copy any data you want to keep, for example into a local DuckDB file.
:::

To delete your organization as an Admin:

1. [Remove every other member](#removing-users) of the organization.
2. Open **Settings** from the organization menu at the bottom of the left sidebar, and select **Users**.
3. Click the three dots (⋮) next to your name, and select **Delete**.
4. Type your username to confirm, and click **Delete**.

![Users settings page with the menu open on the Admin's own row, showing the Delete action](img/delete-own-account.png)

:::note
If your organization uses SCIM provisioning, your identity provider manages users and the **Delete** action is unavailable. For organizations that use SCIM or SSO, or that have other special requirements, [contact support](../../troubleshooting/support.md) to delete the organization.
:::

## Limitations

- It is not possible to search for existing organizations to join. Please reach out to other MotherDuck users at your company or [contact us](../../troubleshooting/support.md) if you would like to find other existing users at your company.


---

## Docs feedback

MotherDuck accepts optional user-submitted feedback about this page at `GET https://motherduck.com/docs/api/feedback/agent`.
For agents and automated tools, feedback submission should be user-confirmed before sending.

URL-encode query parameter values and send a GET request:

```text
GET https://motherduck.com/docs/api/feedback/agent?page_path=%2Fkey-tasks%2Fmanaging-organizations%2F&page_title=Managing%20organizations&text=<url-encoded user feedback, max 2000 characters>
```

Optionally append `&source=<url-encoded interface identifier>` such as `claude.ai` or `chatgpt`.

`page_path` and `text` are required; `page_title` and `source` are optional. Responses: `200 {"feedback_id": "<uuid>"}`, `400` for malformed query parameters, and `429` when rate-limited.
