> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/account-and-administration/organization-details/about-organizations.md).

# About organizations

This page explains why you would split your listings into several organizations, and how to choose a structure.

## What an organization is

An organization is a workspace inside Guestway. Each organization has its own listings, team members and settings. What one team sees and manages stays separate from another team.

A new organization starts with all your listings, and you remove the ones that do not belong. That way, you tailor the workspace to one region, one building or one brand.

You can create as many organizations as you need. They can share team members, but each one keeps its own operational focus.

## Structure by region

Group listings by area, so local teams only see what they operate. For example:

* **East Region**: the listings in the eastern area
* **West Region**: the listings in the western area
* **South Region**: the listings in the southern area

The inbox, cleaning tasks, smart locks and analytics then stay regional, with no noise from properties a local team does not work on.

## Structure by building

Create one organization for each building of your portfolio, for example **123 Main Street** with every unit at that address.

This works well when you have teams on site, access control for one building, or services that only one property offers.

## Structure by sub-brand

If your company has several brands or price levels, give each one its own organization, for example **Luxury Suites**, **Budget Rentals** and **Corporate Stays**.

Branding, guest communication and reporting stay separate for each brand, and team members can still work in more than one organization.

## How to choose a structure

* **Start simple.** If you are not sure how to split, begin with one organization for everything. You can add organizations later, when your operations grow.
* **Match the split to your teams.** If the same people manage all your listings, one organization is usually enough. Split only when different teams, partners or brands must not see each other's data.
* **Combine criteria when you need to.** You can mix approaches, for example one organization per region inside a larger split by brand.
* **Use hubs for oversight.** With many organizations, a hub gives managers one place to follow the whole portfolio. See [About hubs](https://docs.guestway.io/account-and-administration/hubs/about-hubs.md).

## Why listings do not move between organizations

A listing in Guestway belongs to one organization. Its reservations, conversations and settings belong to that organization too. Guestway cannot move a listing with its data from one organization to another.

You can still work with a listing in another organization of your holding. Connect the same PMS account in that organization, and subscribe the listing there. Guestway then makes a new listing in that organization. What your PMS syncs comes into the new organization. What you set up for the listing in Guestway does not come with it. The first organization keeps its own listing, with its data and settings.

The settings of an organization do not move either. Each organization has its own branding, automations and guest journey. What the holding shares stays the same for every organization: the holding owners, the holding roles and the shared hubs. Automation schedules are the exception: you can copy them to another organization of your holding.

The same is true for a whole organization. You cannot delete an organization, or move it out of its holding.

This is why it helps to choose the structure before you set up your listings in detail.

## Related

* [How to create an organization](https://docs.guestway.io/account-and-administration/holding-settings/how-to-create-an-organization.md)
* [How to choose which listings and devices sync](https://docs.guestway.io/integrations/integrations/how-to-choose-which-listings-and-devices-sync.md)
* [What syncs from your PMS](https://docs.guestway.io/integrations/property-management-systems/what-syncs-from-your-pms.md)
* [How to export and import schedules](https://docs.guestway.io/reservations-and-operations/automations/how-to-export-and-import-schedules.md)
* [Organization details](https://docs.guestway.io/account-and-administration/organization-details.md)
* [Hubs](https://docs.guestway.io/account-and-administration/hubs.md)
* [Holding settings](https://docs.guestway.io/account-and-administration/holding-settings.md)
* [Property management systems](https://docs.guestway.io/integrations/property-management-systems.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guestway.io/account-and-administration/organization-details/about-organizations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
