Organizations
Run the organizations you own or belong to — server bags, tokens, teams and settings, one console for every organization instead of one per workspace.
An organization is an account with people in it.
An organization owns work the way a person does — products, personas, buckets, keys. The difference is that several humans can act for it, so somebody has to decide who they are and what they may do. This is the place that decision is made.
A workspace switcher is not an admin console.
Organization administration used to sit one level down inside a hub workspace, in the same rail as everything that workspace owns. It is its own job, done by different people at different times than the building is — and a job that owns your people and your keys has earned its own address.
Four topics, per organization.
Server bags
arbitrary key → JSON config values, read at runtime by what the organization runs.
Tokens
storage-access tokens the organization owns, each with its own isolated bucket.
Teams
the groups inside it, the same teams the rest of the hub hands work to, and who belongs to each.
Settings
the organization’s own profile: what it is called, how it is addressed, and how it appears elsewhere.
What is not here is as deliberate: auth, feature flags and sign-in apps are configured per product, so they sit on the product’s rail rather than the organization’s.
Pick the organization, then the topic.
- Pick an organization from the root list — every one you own or belong to is there.
- Choose the topic you came for. The rail keeps the organization selected while you work, so you never have to check which one you are editing.
- Change it once. Every site in the hub reads the same organization, so what you set here is what all of them see.