What an organization is
An organization (company) is the tenant record that owns everything a business configures in QUE: its services, staff, locations, resources, bookings, customers, domains, payment accounts, workflows, webhooks, and notification templates. The organization's slug is its permanent public identity and drives the public booking URL at /u/:slug.
What it holds
| Asset | How the tenant owns it |
|---|---|
| Public booking URL | https://que.qubickle.com/u/:slug — validated server-side on every request |
| Custom domains | Tenant domain records with DNS verification before traffic is served |
| Payment accounts | Connected provider accounts (Stripe, PayPal, 2Checkout, Authorize.Net) scoped to the company |
| Webhooks | Enabled webhooks with company_id; fanout dispatches only that tenant's events |
| Settings | Currency, payment provider defaults, notification toggles, theme |
The tenant boundary
Tenant isolation is enforced at the database through row-level security: every query runs under the tenant's role, and the application service layer never assumes authorization the database did not verify. A webhook, a staff login, or a customer view can only ever reach rows belonging to its own tenant. A second tenant's identity attempting a cross-read receives an error, not data. The dedicated Tenant isolation page describes the controls and the verification procedure.
One authority context at a time
A person can hold staff rights on one tenant and ownership on another, but the active interface always represents a single authority context. Switching contexts is explicit; nothing is merged across tenants in the interface.