---
title: Organizations
slug: organizations
description: Create and manage organizations to structure teams, control access, and manage credit and data consumption.
image: https://archbee-image-uploads.s3.amazonaws.com/oAyFj2GHlBeBVWF5OAir2/6S1mZLnDSr61QkDw28NsN_1.png
docTags: 
createdAt: 2025-02-03T13:28:13.882Z
---

Organizations are the basic containers into which all scenarios, users, and data belong.&#x20;

Organizations usually represent a company that is a Make customer or partner. Each organization has separate pricing plan and billing. This means that you can also monitor your credits and data consumption for each organization separately.

Each organization allows you to select the geographical location of the data center where the organization's data will be stored and processed. Currently, Make supports two data center locations:

- United States (US)
- European Union (EU)

:::hint{type="info"}
The geographical location that you select for an organization does not represent where your company or your users are located, but where the data center that stores and processes your data is located.
:::

We recommend that you select the location closest to you to ensure low latency.

:::hint{type="warning"}
You cannot change the location of the data center after you create the organization.
:::

## Create an organization

Any user can create their own organization, even if they are already a member of another organization.

:::::WorkflowBlock
:::WorkflowBlockItem
Click on your username in the top-right menu.
:::

:::WorkflowBlockItem
Select **Profile&#x20;**&#x66;rom the dropdown.
:::

:::WorkflowBlockItem
In the **Organizations&#x20;**&#x74;ab, click the **Create organization** button in the top-right corner.

![](https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/RwlysHXUm57D4duBZpuQk-20251001-150009.png)
:::

::::WorkflowBlockItem
In the dialog, enter the details of the new organization.&#x20;

- The **Organization name.&#x20;**&#x54;he name must be between 1 and 128 characters long. Use only letters, numbers, spaces, and allowed special characters. Names can't start or end with spaces.
- The **Region** field represents the location of the data center that will store and process your data. 
- The **Timezone** field represents the time zone used for scheduling scenarios and parsing dates.
- The **Country** field represents your physical location, but is currently not used by Make in any way.

:::hint{type="info"}
If you have multiple affiliate partners as team members of your organization, you can set the affiliate partner for shared scenarios.

::Image[]{src="https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/Ct5skiaIpPHHCp7U_DzoS-20260316-154337.png" size="44" width="376" height="308" position="flex-start" darkWidth="376" darkHeight="308" showCaption="false"}
:::
::::

:::WorkflowBlockItem
Click the **Save&#x20;**&#x62;utton.&#x20;
:::
:::::

:::hint{type="info"}
By default, the organization is on a Free plan and has one team, called **My Team**.
:::

## Add users to an organization

To add users to an organization, you must be the **owner** or an **admin** of the organization. For more details about roles, refer to [organization roles](docId\:Gqsh74OTRRqUr-5Z2ZRYh).

::::WorkflowBlock
:::WorkflowBlockItem
In the left sidebar, click **Org**.
:::

:::WorkflowBlockItem
Click the **Org Users&#x20;**&#x74;ab.
:::

:::WorkflowBlockItem
Click the **Invite user&#x20;**&#x62;utton in the top-right corner.&#x20;

![](https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/khihAB9fC1_-vkogPBdNy-20251001-151129.png)
:::

:::WorkflowBlockItem
In the dialog, enter the user's details.&#x20;

- **Email**: The invited user's email address.
- **Name**: The name of the user, which the user can change after accepting the invitation.
- **Team**: The user's team (**My Team** by default).
- **Role**: The user's [role in the organization](docId\:Gqsh74OTRRqUr-5Z2ZRYh).
- **Note**: An optional custom message to add to the invitation email.
:::

:::WorkflowBlockItem
Click the **Save&#x20;**&#x62;utton.
:::
::::

The user will receive an invitation email with an **Accept invitation** button.

When the user accepts the invitation, Make adds them to the organization.

:::hint{type="info"}
The invitation expires in 7 days. If the invited user does not accept the invitation:

1. Remove the invited user from your organization.&#x20;
2. Send a new invitation.
:::

## Remove a user

To remove users from an organization, you must be the **owner** or an **admin** of the organization.

::::WorkflowBlock
:::WorkflowBlockItem
In the left sidebar, click **Org.**
:::

:::WorkflowBlockItem
Click the **Org Users&#x20;**&#x74;ab.
:::

:::WorkflowBlockItem
Click the role in the **Role&#x20;**&#x63;olumn and select **Remove&#x20;**&#x66;rom the dropdown.&#x20;

::Image[]{src="https://app.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/3KjTW6Bj7wJ69r42PLBuT-20251001-152800.png" size="96" width="1103" height="435" position="center" darkWidth="1103" darkHeight="435" showCaption="false"}
:::

:::WorkflowBlockItem
Click th&#x65;**&#x20;Remove user** button.&#x20;
:::
::::

## Organization roles

<font color="#0C121D">O</font><font color="#0C121D">rganization roles and team roles control what you can access and manage in Make.</font>

<font color="#0C121D">An organization role controls organization-wide settings and resources. A team role controls resources that belong to a specific team.</font>

<font color="#0C121D">Owner and Admin include access to all standard teams, which gives implicit Team Admin access in those teams. A custom organization role with the **View all teams** permission has the same effect. For every other organization role, access to scenarios and other team-owned resources depends on the user's role in each team.</font>

<font color="#0C121D">Feature availability also depends on the organization's plan. To view the complete, current permission set for a role, go to **Org** &gt; **User roles**, select **Organization roles** or **Team roles**, and select a role.</font>

The following table describes actions that members of different organizational roles can perform.

For information about team roles, [read the article about teams](docId\:btahAzLP8hMLnPlpMTblN).

| **Role**          | **Permissions**                                                                                                                                                                                                                                                                                                        |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Owner**         | Has full organization access. Is the only role that can transfer ownership or delete the organization. Manages users, teams, custom roles, organization settings and resources, apps, agents, connected systems, audit logs, billing, and subscription settings. Has implicit Team Admin access in all standard teams. |
| **Admin**         | Administers organization-wide settings, including users, teams, custom roles, organization resources, apps, agents, connected systems, audit logs, billing, and subscription settings. Can't transfer ownership or delete the organization. Has implicit Team Admin access in all standard teams.                      |
| **Member**        | Views organization details, users, credit usage, installed apps, templates, variables, and analytics. Uses connected systems and accesses their own private space. Access to shared team resources depends on their team role.                                                                                         |
| **Accountant**    | Views organization, user, credit, installed-app, template, billing, payment, and payment-method information. Can't change billing or organization settings. Access to team resources depends on their team role.                                                                                                       |
| **App Developer** | Views relevant organization information. Installs and manages apps, and creates or uses agents and connected systems. Access to team resources depends on their team role.                                                                                                                                             |
| **Guest**         | Views basic organization details. Mainly receives credential requests; Team Guest provides the request-specific access. Guest alone doesn't grant general access to team data.                                                                                                                                         |

Custom organization roles let you assign a tailored set of permissions instead of a default role. To learn more, see [Custom roles](docId\:Wro0FboAoI9vT6fvcBa22).

## Switch organizations

If you're a member of multiple organizations, you can change the active organization by clicking on your name in the top-right corner and selecting another organization.&#x20;

::Image[]{src="https://app.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/unez1bQ4rcGX07DK3s4BS-20251001-155222.png" size="42" width="292" height="256" position="center" darkWidth="292" darkHeight="256" showCaption="false"}

## Transfer ownership

When you create an organization, you automatically become the owner of the organization. Organization owners can manage and access all teams in an organization. An organization can have only one owner.&#x20;

If you are the owner of an organization, you can transfer ownership to any member of your organization:

::::WorkflowBlock
:::WorkflowBlockItem
In the left sidebar, click **Org**.
:::

:::WorkflowBlockItem
Click on your username in the top-right corner.&#x20;
:::

:::WorkflowBlockItem
Go to  **Organization settings** > **Transfer ownership**.



::Image[]{src="https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/nGKcLajFsglo6YN17Rqs1_image.png" size="50" isUploading="false" width="545" height="505" darkWidth="545" darkHeight="505" position="flex-start" showCaption="false"}
:::

:::WorkflowBlockItem
In the **User&#x20;**&#x64;ropdown, select the organization member you want to be the owner of the organization.&#x20;

All current organization members appear in the menu. Once a new member accepts the invitation, you can transfer ownership to them.
:::

:::WorkflowBlockItem
Click **Save**.
:::
::::

A purple pop-up appears confirming that ownership has been transferred successfully.

:::hint{type="warning"}
Ownership transfers can only be performed by existing organization owners. If you do not have owner access, reach out to our [Support](https://www.make.com/en/ticket).
:::

## Delete an organization

You can delete an organization only if you are the owner of the organization. You can't delete an organization owned by other users.

:::::WorkflowBlock
:::WorkflowBlockItem
Click on your username in the top-right corner.&#x20;
:::

:::WorkflowBlockItem
Select **Profile**.
:::

:::WorkflowBlockItem
In the **Organizations** tab, you will see a list of all organizations you have access to.&#x20;
:::

:::WorkflowBlockItem
Click the three dots next to the organization you want to delete, then **Delete**.

![](https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/qR_Te4W9BQqR1KjtsvEoh-20251002-152136.png)
:::

::::WorkflowBlockItem
In the dialog, type the name of the organization you want to delete, then click **Delete organization**.

:::hint{type="warning"}
You can't undo this action. Your organization will be permanently deleted and it can't be retrieved.
:::
::::
:::::

Your organization has been deleted.&#x20;
