Hotels and branches (Structures) #
A structure (or entity) is one hotel. The demo has one: LemonTree Hyderabad (reference code LTHYD, property role LTH_HYD_PR). Every task belongs to an entity, and people only see the entities they belong to.
Why it matters #
- Separate data per hotel. Staff of one hotel see that hotel's tasks.
- The right approvers. A step is approved only by people of the task's hotel.
- Figures per hotel. Dashboards and reports show the hotel selected in the header.
Before you start #
Each entity needs its own property role (role type Property Role). Create it under Staff & Guests → User Roles (Roles). Name it after the hotel's code, for example LTH_HYD_PR.
Add a hotel #
- Open Structures from the admin menu and press Create Entity.
- Fill in the details. Example for a second hotel:
| Field | What to enter | Example |
|---|---|---|
| Entity Name | The full name, as on screens and reports | LemonTree Gachibowli |
| Location | Town or area | Gachibowli, Hyderabad |
| Phone | Main number | 040 … |
| Description | A short note | LemonTree Gachibowli – second hotel |
| Reference Code | A short unique code | LTGCB |
| User Role Name | The property role you created | LTH_GCB_PR |
- Press Save Changes. It appears under Select Hotel for everyone who holds its property role.
Give people access #
A user belongs to a hotel when they hold its property role. Give it when you create or edit the user (Users). People who work across hotels get each hotel's property role and switch in the header.
Common mistakes #
- A user sees no tasks at all: they have no property role.
- The selector is missing a hotel: the user lacks that hotel's property role.
- Sharing one property role between two hotels: their data gets mixed.
Next: 3. Roles