> 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/settings/holding-settings.md).
# Holding settings
The holding settings manage the organizations, owners, shared hubs, users and invoicing of a holding.
{% hint style="info" %}
**Requirements**
* You are an owner of the holding.
{% endhint %}
A holding is the parent account above your organizations. It groups more than one organization, for example different brands, regions or legal entities, under one account.
The holding settings are at your profile picture (top right) → **Profile organization** → **Holding**. The menu has these items: **General**, **Organizations**, **Hubs**, **Owners**, **All users** and **Invoicing**.
## General
The name of the holding, and security policies for the whole holding, for example 2FA enforcement.
## Organizations
All organizations of the holding. You can create a new organization in the holding here.
## Hubs
Shared hubs. All users of the holding see these hubs. [Personal hubs](https://docs.guestway.io/settings/personal-settings/hubs) are private to one user.
## Owners
The owners of the holding. You can add and remove owners. Owners manage the whole holding and its organizations.
## All users
The **Users across your organizations** page shows each person in the organizations of the holding.
| Tab | What it shows |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Platform users** | The people who work in the Guestway platform. A holding owner has an **Owner** badge next to the name. |
| **Cleaners** | The people who only use the cleaning app. |
| **Roles** | The roles that every organization of the holding has: the built-in roles and the roles for the whole holding. **Create role** makes a new role for the whole holding. Roles of one organization are in the **Roles** tab of that organization. |
Click a person to open their page. The page shows the organizations in two lists:
| List | What it shows |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Member of** | The organizations that the person is a user of. You can change their roles there. |
| **Can be added to** | The other organizations of the holding. Select a role and click **Add**. The person is a user of that organization at once, without an invite to accept, and gets an email about it. |
You cannot remove a holding owner from an organization.
When you go back with **Back to all users**, the tab that you used stays selected.
## Invoicing
Stripe invoicing and ID verification usage reports.
* Sign in to **Stripe** to see invoices and billing details, edit your billing information and download invoices.
* Download a monthly **CSV** of ID verification usage: reservation codes, stay dates and verification counts. Use it to reconcile the verification charges for the holding.
## Related
* Users
* [Personal hubs](https://docs.guestway.io/settings/personal-settings/hubs)
---
# 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/settings/holding-settings.md?ask=&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.
