> 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/onboarding/creating-organizations.md).

# Creating Organizations

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/zklzy84top>" %}

***

### What is an Organization?

Think of an Organization as a dedicated workspace inside Guestway. Each workspace has its own set of listings, team members, and settings — so what one team sees and manages stays separate from another.

By default, a new Organization includes **all** your listings. From there, you deselect the listings that don't belong, tailoring the workspace to a specific region, building, or brand.

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

***

### Ways to structure your Organizations

There's no single right answer — the best structure depends on how your operations are split. Most Guestway users organize along one of the following lines.

#### By region

Group listings geographically so local teams only see what they operate.

**Example:**

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

This keeps inboxes, cleaning tasks, smart locks, and analytics regional — no noise from properties a local team doesn't touch.

#### By building

Create one Organization per building in your portfolio.

**Example:**

* **123 Main Street Organization** — every unit at that address

Useful when you have on-site teams, building-specific access control, or services unique to a single property.

#### By subbrand

If your company operates under multiple brands or price tiers, split them into their own Organizations.

**Example:**

* **Luxury Suites** Organization
* **Budget Rentals** Organization
* **Corporate Stays** Organization

Branding, guest communication templates, and reporting stay distinct per brand, while team members can still be shared across Organizations where needed.

***

### Tips for choosing a structure

* **Start simple.** If you're not sure how to split things, begin with a single Organization covering everything. You can create more Organizations later as 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 shouldn't see each other's data.
* **Combine criteria when needed.** Nothing stops you from mixing approaches — for example, one Organization per region inside a larger subbrand split.
* **Use Hubs for oversight.** Even with many Organizations, Hubs gives leadership or regional managers a single place to watch the whole portfolio.

***

### Related pages

* [Sign-up Registration](https://docs.guestway.io/onboarding/sign-up-registration) — create your Guestway account before setting up your first Organization.
* [Property Management Systems](https://docs.guestway.io/integrations/property-management-systems) — connect your PMS so listings sync into your Organizations.
* [Hubs](https://docs.guestway.io/settings/personal-settings/hubs) - group multiple Organizations into one view.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.guestway.io/onboarding/creating-organizations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.