Settings

The operator portfolio

Today's position across every property your organisation manages for somebody else — one read-only screen, composed without crossing a tenant boundary.

Last updated

Who this is for: Owner at a management company — requires org.portfolio.read. Where: Settings → Portfolio

Note

If you own the hotels you run, this screen is not for you. It composes properties across other organisations that have delegated a role to your roster. A single-organisation house sees an empty state here for ever, and wants Portfolio roll-up in Revenue instead.

An operator's morning question is not "how did that hotel do last quarter" — it is "where is my attention needed today". This screen answers it: every managed property, in one list, with the four numbers that decide where you look first.

It is strictly read-only. Nothing on it can be changed, and there is no action to take from it — you switch into the property and work there.

Read the summary#

The four tiles at the top are the whole portfolio at once:

Tile What it counts
Properties Hotels you reach across every managed organisation
Managed orgs The client organisations behind them
In-house Guests currently checked in, everywhere
Arrivals today Expected arrivals, everywhere

Read a property slice#

Below the tiles, one card per managed organisation, and inside it one row per hotel: Rooms, In-house, Arrivals, Departures.

The grouping is by organisation rather than by hotel because that is the unit the relationship is negotiated in — a link, a grant and a revocation all act on the organisation, not on one of its hotels.

When a slice says "unavailable"#

A card flagged unavailable, and the amber banner above the list, mean one managed organisation could not be read on this pass. The rest of the portfolio still renders with real numbers.

This is deliberate: a fan-out across other people's organisations will occasionally have one participant unreachable, and blanking the whole screen for it would be worse than saying which one is missing. Refresh, and if a slice stays unavailable, check that its operator link is still active on Operator links.

Important

The portfolio never crosses a tenant boundary. Each slice is read inside the managed organisation's own scope, authorised by your roster membership there — the same authorisation that lets you open the property directly. If a grant is revoked, the slice disappears from this screen at the same moment the property disappears from your switcher. There is no back door here, and no aggregate that survives the access it was built from.

What's next#