Headquarter overview

Who this is for: Owner — every Headquarter permission is anchored on org.manage, so no other default role reaches this app. Where: Headquarter (its own sidebar group, once installed)

Headquarter is a second kind of cross-property roll-up, and a different one from Operator links. Operator links model operational management — one organisation's staff actually working inside another's hotels, with delegated roles. Headquarter models reporting only: a consortium, a franchise, or a referral group made of properties that stay under their own management and never share staff, but still want one dashboard across the group. No membership is delegated and nobody's role changes — a member property just opts a hotel's KPIs into somebody else's roll-up.

Quan trọng

Headquarter is installable, not on by default. Like Revenue and the Integration Hub, a new property starts without it. An account that does not see a Headquarter group in the sidebar is most likely looking at a property where nobody has installed it yet — see Enabling apps for a property.

The two sides of a group#

	The owning organisation	A member property
Creates the group	✓
Invites a property, by email	✓
Picks which of its own hotels to enroll		✓, at accept time
Reads the roll-up dashboard	✓	✗ — a member does not get a dashboard view of the group it joined
Can end the membership	✓	✓, for its own membership only

Inviting by email rather than by organisation id is deliberate: unlike an operator link, where the two organisations already have a relationship and can exchange an id out of band, a headquarter group is often built from businesses that have never shared a tenant identifier before. An admin's email address is the thing they actually have.

A property that both owns groups and belongs to somebody else's sees both halves on the same Groups screen — the same account can be the headquarters for one relationship and a member in another.

Quan trọng

Accepting an invitation is the entire authorization. Once a property's admin accepts, the owning organisation's dashboard can read that hotel's occupancy, ADR, RevPAR and room revenue — without the viewing account needing any membership in the member's own organisation. Revoking (from either side) removes that access at the same moment, the same way leaving an operator link does.

What's in this section#

• Groups — create a group, invite properties by email, and accept or decline an invitation addressed to you. headquarter.group.manage, headquarter.member.manage
• Dashboard — the roll-up itself: one card per active member property. headquarter.read

There is no Headquarter landing screen of its own. Opening the group takes you to Dashboard.

How it connects#

The roll-up never crosses a tenant boundary. Each member's slice is read inside that property's own organisation scope, exactly the pattern the pre-app portfolio home and the operator portfolio both use — one scoped read per member, a failed slice flagged rather than aborting the whole dashboard, and no query that spans two organisations.

This is not the same relationship as Operator links. Operator links and the delegation roster hands one organisation's staff actual roles inside another's hotels. Headquarter hands nothing — no login, no role, no write access — it only lets a hotel's own summary figures be read by a group it opted into.