An organization can be looked up by the reference ?org= carries

FixSecurityService
Shipped
August 26, 2026 at 8:41 PM UTC
Author
Kamo
Commit
ef2721f

GET /org/ref/{ref} — the same projected record as /org/domain/{host}, for an organization named by its id or its web alias. Nothing could answer for one. The shell takes a tab's tenant from ?org= on its URL, because a URL is the only per-tab thing a document request carries, and that reference stopped being a hostname when a domain became optional. The front end had only the by-host lookup to reach for, so it built the API host out of the reference — `https://api.wienerschnitzel` — asked a host that does not exist, failed three times, and fell back to rendering the platform. Every asset that organization had chosen was provisioned correctly and never requested: GET **************** [retry] org err='fetch failed' isAbort=false willRetryIn=250ms [retry] org failed after 804ms attempts=3 [TypeError: fetch failed] Session-guarded, unlike the by-host lookup beside it. That one is open because naming an organization by hostname means knowing a hostname it already answers on. An alias is guessable — "acme", "kia-kaha" — and this returns the full record: features, labels, branding, flags. Open, it would make every organization's configuration enumerable, which is precisely what PublicOrgBrandingController refuses and why that endpoint serves branding only. A session does not make the reference a credential: it selects which organization to describe, and every right in the workspace is still proven per request. Same projection as the by-host lookup rather than a similar one, domains join-fetched — a record without `domain` throws in the client's fromJSON before the shell renders, which is a blank page rather than a missing field.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing