Console Guides
Three consoles, one BuildWithHQ identity
How Admin, Developer, and Operations divide navigation without dividing authentication or authorization.
Login
Shared
Sessions
Shared
Permissions
Existing server rules
BuildWithHQ separates the builder experience into three focused consoles. This is a navigation and design split: your login, session, account membership, app ownership, roles, DataRoles, locations, and server permissions remain the same.
| Console | Primary job | Production home |
|---|---|---|
| Admin Console | People, billing, branding, communications, security, and account governance. | hello.buildwithhq.com |
| Developer Console | SaaS apps, templates, AI harnesses, appliances, integrations, API clients, and marketplace publishing. | dev.buildwithhq.com |
| Operations Console | Provisioning, runtime health, domains, backups, logs, analytics, storage, and AI operations. | ops.buildwithhq.com |
What stays shared
- the same sign-in, MFA, recovery, invitation, and account-selection flow;
- the same browser session and account/app context;
- the same backend APIs and stored-procedure-backed application services;
- the same authorization checks on every request; and
- the same audit and correlation evidence.
Navigation is not permission
A link appearing in a console does not grant access, and hiding a link is not a security boundary. Each service verifies the signed-in identity, account/app relationship, and required capability server-side.
Note
You may use all three consoles with the same identity. What you can view or change remains limited by the permissions already assigned to you.
Did this page answer your question?Tell us what’s missing