> 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/hubs/about-hubs.md).

# About hubs

This page explains why you would group organizations in a hub, and how to choose the hubs that fit your company.

## A view above your organizations

An organization groups a set of listings, teams and operations. A hub groups several organizations. It is the top-level view of your business, useful when your operations span regions, brands or business units.

From a hub, you see everything in its organizations at once. When you need to focus, you go back to a single organization.

## Common hub setups

There is no single right answer. Pick a structure that mirrors how your company is organized, and how you work day to day. For example:

* A **North America hub** with every organization that operates in the United States.
* A **Europe hub** with every organization that operates in the European Union.
* A **Global hub** with every organization, in the United States and in Europe.

Match hubs to your reporting lines. If one director owns the European portfolio and another owns the American one, each of them can have a hub with exactly their responsibility.

Hubs sit on top of the organization structure that you already use: by region, by building or by sub-brand. See [About organizations](https://docs.guestway.io/account-and-administration/organization-details/about-organizations.md).

## Personal and shared hubs

A personal hub is your own view. Nobody else sees it, so you can group organizations the way you like to work.

A shared hub is made by a holding owner, and all users of the holding see it. It gives the whole team the same grouping, for example one hub per region.

## What stays in one organization

A hub is made for daily work across organizations: the inbox, reservations, reviews and analytics. Settings and new items belong to exactly one organization, so you change and create them after you switch to that organization. The AI center and cleaning are also used per organization, not in a hub.

## Related

* [How to create a hub](https://docs.guestway.io/account-and-administration/hubs/how-to-create-a-hub.md)
* [Hubs](https://docs.guestway.io/account-and-administration/hubs.md)
* [About organizations](https://docs.guestway.io/account-and-administration/organization-details/about-organizations.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/hubs/about-hubs.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.
