Accounts¶
Seeded usernames for each system. Passwords are not stored in this wiki — ask a developer or check the team password manager.
Never share passwords here
This wiki is read-only and visible to the whole team. Passwords belong in a secrets manager (1Password / Azure Key Vault), not in Markdown.
HappyBean Legacy (subdomain-per-tenant)¶
Each tenant has its own users. The admin username exists separately on each tenant — they are not the same account.
Production (*.happybean.app)¶
| URL | Username | Notes |
|---|---|---|
| https://admin.happybean.app | admin |
Host-level admin — manages all tenants |
| https://demo.happybean.app | admin |
Demo tenant — safe for sales demos and training |
https://<customer>.happybean.app |
varies | Each customer has their own users |
Dev¶
Same model as production — separate admin and demo tenants exist on the dev environment, each with the same admin username. Ask a developer for the current dev subdomain pattern.
HappyBean 2.0 (new stack — single web URL, email-based login)¶
Login by email address, not by tenant subdomain. The system shows you which tenants you belong to and routes you accordingly.
| Account | Scope | |
|---|---|---|
| Tenant admin | admin@happybean.app |
Default tenant — full admin within that tenant |
| Host admin | host@happybean.app |
Host-level (tenant_id = 0) — manages all tenants |
Seeded by
python -m app.seed. Default passwords come fromADMIN_PASSWORD/HOST_PASSWORDenv vars on the API App Service — ask a developer.
Mobile¶
Same accounts as HappyBean 2.0 above (the mobile app uses the same API).