Authentication and access
Share the app. Skip the authentication project. Hub checks identity and access before a request reaches the app, so the app ships without login, sessions, invitations, password resets or user management.
One app. The right audience.
Org
Everyone in your Hub org, after one login. Nobody else.
Public
No login. Anyone with the address can open it.
Coming next: only me, selected people, secure share links.
Access belongs to the instance. Production, staging and demos each get their own rule, and a change needs no rebuild.
| Instance | Access |
|---|---|
| customer-portal/prod | org: anyone signed in to acme |
| customer-portal/staging | org |
| inventory/prod | org |
| product-demo/prod | public: no login |
People sign in to Hub once. Every app in the org inherits it.
Ten tools do not need ten account systems. Remove someone from the org once, and every app is closed to them.
The app can know who opened it.
After access is approved, Hub passes the person's identity to the app in two headers:
X-Hub-EmailX-Hub-Name
Use them for greetings, attribution or the app's own permissions. Hub decides who may reach the app; the app decides what they may do inside it.
Opening an app and operating it are separate permissions. Access controls who may use the software. Org roles (viewer, member, admin, owner) control what someone may do in Hub itself.
A viewer reads releases and logs without getting a shell. An admin manages access without becoming the owner.