Skip to content
Stay N Host Help

Workspaces and isolation

A workspace is your company inside Stay N Host: your properties, bookings, guests, team, and books. It is also a hard boundary - every piece of data belongs to exactly one workspace, and nothing crosses it.

The seal is in the database, not the screens

Section titled “The seal is in the database, not the screens”

Isolation isn’t a filter the app remembers to apply. Every table carries the workspace it belongs to, and the database itself enforces row-level security on every query - a request made under one workspace physically cannot read or write another’s rows, even if the application code had a bug that tried. The same rule binds automations, reports, exports, and the API: there is no query path that skips it.

This is why you’ll never see a “shared across companies” feature, and why support questions like “can the other operator see my rates?” have a one-word answer.

People who belong to several workspaces

Section titled “People who belong to several workspaces”

A person is not a workspace. Your account can hold seats in multiple workspaces - say, an accountant serving three operators, or an owner with units under two managers. Each seat has its own role in that workspace, and the seats know nothing of each other:

  • The workspace switcher moves you between them; you are in exactly one at a time.
  • Your sidebar, permissions, and data change completely on switch - the same person can be an Admin in one workspace and a read-only External Accountant in another.
  • Notifications, drafts, and preferences are per-seat, not per-person.

The seal at the edges

Section titled “The seal at the edges”

The boundary holds even where no one is signed in. Every guest-facing link - the quote, the ID upload, the proposal, the guest app - resolves through its token to exactly one workspace’s one record, and every failure looks identical: a wrong, expired, or revoked token shows the same plain not-found page. A prober can’t learn which tokens are real, whose data sits behind one, or that a workspace exists at all.

What the boundary means day to day

Section titled “What the boundary means day to day”
  • Configuration is per-workspace. Currency, timezone, payment channels, roles, agent rules, fees - set in one workspace, invisible in another.
  • Billing is per-workspace. Each workspace has its own plan and subscription.
  • The audit trail is per-workspace. Your Audit screen shows your workspace’s actions and nobody else’s.