Security deep-dive

True of the code,
not the brochure.

How permissions resolve, how tenants stay apart, and what happens to a request before it reads anything.

Permission resolver

Try a request.

Pick a person. Watch the scope chain resolve, with per-channel overwrites applied last.

POST #release → 201. Allowed at every layer.

Real time, without a refresh
One socket carries messages, typing, presence and voice state. Presence is reference-counted per account.
Permissions that resolve
A closed catalogue shared by the server and every client, resolved through a scope chain.
Nothing crosses a tenant boundary
Every route resolves the organization from the session first; a foreign id answers 404.
Limits you can read first
Pricing reads the same plan catalogue the server enforces.