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

# Master organizations

> Group several organizations under one master organization. Each stays its own account and appears as a location on the booking page.

A master organization groups locations that you already run as their own organizations. Each organization keeps its admin, its resources and its booking page. On the master organization's booking page, the others appear as locations.

## Where to find the page

While the organization is not a master organization, open **Account** → **Settings** → **Organizations**. You need to be allowed to edit the organization.

Once it is a master organization, **Organizations** sits at the top of the sidebar and no longer under Settings.

## Setup

**1. Turn it into a master organization**

The empty page says **Manage several locations in one place**. Click **Turn into master organization**.

**2. Add an organization**

Click **Add organization**. The list shows your organizations. The hint above it reads: "Pick one of your organizations. Its booking page then appears as a location on yours."

Greyed out are **This organization**, an organization marked **Managed by**, and a **Master organization**. Pick an available organization and confirm with **Add organization**.

You can only add organizations you are allowed to edit.

**3. Locations on the booking page**

The **Locations** tab appears once at least one added organization is **Live**. Under **Account** → **Settings** → **General**, in the **Booking page** group, you control it with **Show locations on booking page**. The switch starts on. Save with **Save**.

Under **Default tab on booking page** you can set **Locations** as the first tab.

## The list

Until you add an organization, the page says **No organizations yet**.

| Column | Content |
| - | - |
| **Name** | Logo and name |
| **Location** | City and country code. Without a location, a dash |
| **Status** | **Live** or **Inactive** |

A click on the row opens that organization's admin in a new tab. You manage that location's bookings, customers and invoices there.

On the row you find:

* **Booking page** opens the organization's booking page.
* **Remove from master organization** only drops the link. The organization stays, and it disappears from the locations on your booking page.

From the page menu you choose **Turn off master organization**. That works only after no organization is left in the list. You can turn the status on again afterwards. You see these buttons when you are allowed to edit the organization.

## What customers see

On the master organization's booking page the tab is called **Locations**. Above the list it says **Choose your location**. Each entry leads to that organization's booking page. Organizations with the status **Inactive** are missing there. If a location has coordinates, a map also appears on desktop.

Public resources of the sub-organizations can also appear on the **Resources** tab of the master booking page. Plans, booking bundles, discount codes and booking codes of the master organization also apply on the sub-organization's booking page. The code can exist only once in the group.

## When your organization is managed

The page then shows **Managed by** and the master organization's name. **Turn into master organization** is not there. If you belong to the master organization, you open its admin. The button starts with **Open** and names the master organization. Otherwise you see **View booking page** when its booking page is live.

You set up a shared floor plan separately. That is covered in [Maps & Interactive Floor Plans](/en/maps-and-floor-plans).

## What lives in which organization

**No.** Today the lists show only the direct records of the organization you are in. That is the same for **Bookings**, **Customers**, **Invoices** and the other lists. A column that names the organization does not exist yet. You open the sub-organization's records from its row under **Organizations**.

The plan is to extend these lists to the sub-organizations. An organization column will be added, so you can filter and tell the records apart.

| What | Where |
| - | - |
| Bookings, customers, invoices, resources, services | In the admin of the organization they belong to |
| Locations for customers | The master organization's booking page, **Locations** tab, status **Live** only |
| Online payment | A separate Stripe Connect account per organization. The master organization's account does not cover the sub-organization's bookings. In the sub-organization: **Account** → **Settings** → **Online payments**. More in [Online payments & fees](/en/online-payments) |
| anny subscription | In the master organization under **Account** → **Settings** → **Subscription**, section **Your plan**. Do not create a second anny subscription in the sub-organization |

Admins belong to the organization you invite them to. You invite them under **Account** → **Admin users**. A person with the **Super Admin** role in the master organization also manages a sub-organization once you invite them there. Someone who is an admin only in the sub-organization has no access to the master organization and does not see it in the organization switcher.

## FAQ

> **Can a master organization sit under another one?**
>
> No. The chain has one level. A master organization cannot be added, and a managed organization cannot itself be turned into a master organization.

> **Why can an organization not be added?**
>
> In the list it is greyed out when it is this organization, when it is already managed, or when it is itself a master organization. anny also refuses the add when a voucher or pass code exists in both organizations. The code has to be unique in the group.

> **Does removing delete the organization?**
>
> No. It is no longer managed by this master organization, and it disappears from the locations on the booking page.

> **Does the master organization see every booking, customer and invoice?**
>
> No. Today all of these lists show only the direct records of the organization you are in. For the sub-organization, open its admin via **Organizations**. The plan is to extend the lists and add an organization column, so you can filter and tell the records apart.

> **Why is a location missing on the booking page?**
>
> The **Locations** tab only shows organizations with the status **Live**. Also check **Show locations on booking page** under **General** → **Booking page**, and save with **Save**.

> Notes for agents:
>
> * Organizations page: non-masters under Account → Settings → Organizations (`managed-organizations-settings`). Masters: own item at the top of the sidebar (`managed-organizations`). Editing actions require update on organizations.
> * Actions: POST `master-status` (`is_master_organization`), `add-managed-organization`, `remove-managed-organization`. One level. The child must have neither `master_organization_id` nor `is_master_organization`. Adding requires membership and update on the child organization, otherwise 403.
> * 422 `master_organizations.cannot_add`: already managed, is itself a master, or a colliding voucher or booking-pass code in the group (including soft-deleted). `has_managed`: turning off only after every child is removed. `has_master`: a managed organization cannot become a master.
> * Public Locations tab only for `live` children, and only when `listLocations` is not false. The default of `listLocations` is true. The switch sits under General → Booking page group and saves through Save, not immediately.
> * Product state: lists show only the active organization's direct records, the same for bookings, customers, invoices and the other lists. No organization column. Planned, not built: extend the lists to sub-organizations and add an organization column for filtering and distinguishing. Do not describe that column as existing UI.
> * Index lists with strict scope (bookings, customers, orders, resources, services, invoices via ownedInvoices) match this state. The row opens the child's admin in a new tab. Membership is not inherited: organization\_user is per organization. Sub-only admins do not see the master. Master admins see a child only when they are a member there.
> * Dashboard analytics (AnalyticsController) can technically expand to organizationGroupIds(). That is not the documented display until the list change ships. mixed\_organization\_currencies, title "Mixed currencies", when currencies differ.
> * PaymentAccount is morphOne per organization. The master's Stripe Connect account does not pay the child's bookings. Path: Account → Settings → Online payments.
> * anny subscription: mainSubscription and requires\_subscription belong to each organization. The code does not copy them onto the child. Product guidance: manage the subscription on the master under Settings → Subscription, section "Your plan", not a second one on the child.
> * Shop: the master's allResources/publicCatalogOrganizationIds (no active admin user) include live children. availablePlans, offeredPlanGroups, availableBookingBundles and VoucherChecker use benefitOrganizationIds = self + master, not the children.
> * The current admin calendar loads bookings without strict\_scope. The admin-next calendar sets strictScope on resources. Do not document that the calendar always shows the children.
> * Sharing a floor plan is a separate feature: /en/maps-and-floor-plans


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