Limit a seat to specific properties

Screen /team · Roles: Admin

Property scoping has two halves, and the Property access panel on the Team screen keeps them side by side because neither makes sense alone: first you choose which roles are scoped, then you grant who can reach what. A scoped role with no grants sees nothing - that is deny-by-default working, but it looks exactly like an outage if you do the first half and forget the second.

1. Click “Give access” first. Pick a person or a whole team, then tick everything they look after: whole properties, or Pick units to select individual units. Ticking a property is a standing grant that also covers units added to it later.

2. Click “Give access (n)” to save. Grants already in place show pre-ticked and locked, so the dialog always shows the true current state.

3. Click “Scoped roles” and tick the roles that should be limited. The dialog states the consequence before you save: anyone holding a scoped role without an assignment sees nothing - no properties, bookings, or tasks - the moment you confirm.

4. Read the panel afterwards. Every scoped role shows as a pill; grants are grouped by person, answering “what can Ali reach?” at a glance. The trash icon revokes a single grant.

Order matters: grants before scoping

Turn on scoping for a role only after its holders have grants. The panel warns you in as many words when a role is scoped and nothing is assigned - and the save is refused outright if scoping a role would blind an admin who has no property access yet.

Two roles resist scoping

The Account Manager role cannot be scoped - money verification is workspace-wide by design. And roles you never scope are simply unaffected: they keep seeing every property, which is the state every workspace starts in (“Off for everyone”).

How it feels to the scoped person

Everywhere in the app - calendar, bookings, housekeeping, money - a scoped seat sees only its assigned properties and units. There is no “restricted” banner; the rest of the portfolio simply does not exist for them.

What’s next

• Grant access to a whole crew at once by assigning a team instead of one person.
• Choose the right role - scoping narrows where a role acts, never what it can do.