The bridge of the starship, if you will. One web page to monitor everything happening across your ambientChat deployment — users, beacons, errors, and the general state of the universe.
#What It Does
The web admin screens are the Admin section of the web interface, namespaced under /admin/*. They provide a centralized dashboard with real-time statistics, error monitoring, and access to every administrative function in the system. If the mobile app is where users interact with their data, the Admin section is where you make sure everything is working properly for everyone.
The dashboard is your landing page — a quick-glance summary of platform health, user activity, and system status. From there, you can drill into any area that needs attention.
#How to Use It
#Web
Accessing the web admin screens:
- Open the web interface in any modern web browser
- Dev environment:
ambientchat-dev.web.app - Production:
app.ambientchat.ai
- Dev environment:
- Sign in with your usual credentials (same login as the mobile app); your account must have a brand user, brand admin or superuser role — the Dashboard opens for all three
- The Admin section appears in the sidebar. You'll land on the Dashboard at
/admin/dashboard— the home screen for all admin activity
Dashboard overview:
The dashboard presents key metrics in a widget layout:
| Widget | What It Shows |
|---|---|
| User Statistics | Total registered users, active users, new signups |
| Partner Counts | Number of partner organizations and their users |
| Beacon Statistics | Total beacons registered, active regions, recent detections |
| Error Monitoring (24h) | Error count and rate over the last 24 hours — the number you want to keep at zero |
| Search Fallback Events | When semantic search falls back to keyword search — indicates embedding gaps |
| Login Analytics | Recent login activity, sign-in methods, failed attempts |
Navigation:
The Admin section of the sidebar lists the web admin screens your role can open (all namespaced under /admin/*; superusers see every one):
| Section | What You'll Find |
|---|---|
| Dashboard | The overview you're looking at right now |
| Users | Search, browse, and manage user accounts |
| Billing | Revenue tracking, tier breakdowns, usage analytics |
| Chat | Conversation audit, message search |
| Scans | Processing queue status, failed jobs, retry controls |
| My Things | Inventory overview across users |
| Beacons | Beacon registry, region management, alert configuration |
| Partners | Partner organization management |
| Configuration | System settings, feature flags, tier definitions |
| Diagnostics | Function health, Firestore inspection, storage stats |
| Audit Log | Complete trail of every admin action with timestamps |
| Settings | Admin console preferences |
| Profile | Your admin profile |
| Delete Account | Account deletion management (with confirmation workflow) |
Role-based access:
Not everyone sees everything. Access is scoped by role:
- Superusers see the full console — every section, every user, every setting
- Brand admins see their organization's users and data, but not system-wide configuration or other organizations' data
- Brand users see the Dashboard and Beacons & Tags for their organization
- Regular users cannot access the admin console at all — opening an admin page takes them to Chat
#Tips & Tricks
- Check the error monitoring widget daily. A spike in errors is the earliest signal that something needs attention. The 24-hour window keeps the view current without overwhelming you with historical noise.
- Search fallback events matter. When the system falls back from semantic search to keyword search, it means some items or documents are missing embeddings. This affects search quality for users. If the count is climbing, investigate the embedding generation pipeline.
- Bookmark the dashboard. It's the fastest way to get a pulse on platform health. Most admin sessions should start here before diving into specific sections.
#Options
| Setting | What It Does | Default |
|---|---|---|
| Dashboard refresh | How often dashboard widgets refresh their data | On page load |
| Theme | Light or dark mode for the admin console | System default |
| Timezone | Display times in your local timezone | Browser timezone |
#Known Limitations
- The web admin screens are web-only. There is no mobile admin app — use a desktop or tablet browser for the best experience.
- Some operations require superuser role. Configuration changes, system diagnostics, and cross-organization data access are restricted to superusers. Brand admins will see these sections grayed out or hidden.
- Dashboard data is not real-time streaming. Widgets update when the page loads or when you manually refresh. For real-time monitoring of specific events, use the Diagnostics section.
- Browser compatibility. The console works best in Chrome, Safari, Firefox, and Edge. Older browsers may not render all dashboard widgets correctly.
#Website acquisition analytics
Superusers can open Admin → Website analytics to follow consented website visits through account creation, checkout and verified first web payment. App Store payments and unattributed payments are reported separately. Development data is labelled, and the public design example uses illustrative data only.
The headline experiment enrolls later homepage visits after a previous measurement choice; the first consented document stays observational. Exposure means the headline is actually in view in a foreground tab.
Set a hypothesis, attribution window, assignment duration, allocation and minimum sample floors, then save the draft before starting. Running settings are locked. You can stop new assignments or pause collection while preserving the historical report. Compare mature cohorts and their uncertainty after the full window; exposures and clicks are diagnostic, not paid conversion. Review refunds, cancellation requests, subscription endings and missing fee/net data before deciding. The console never declares a winner automatically.
#Version History
| Version | Date | What Changed |
|---|---|---|
| 8 | 2026-11-14 | Added the Website analytics console, mature paid-conversion interpretation and locked experiment controls. (AMB-3292) |
| 7 | 2026-10-29 | Every account deletion now records who asked for it — the user or a named admin. The admin dashboard's phantom-account cleanup never touches guest accounts, logs which admin removed each login, and its dry run can no longer delete anything by mistake AMB-2811 |
| 6 | 2026-10-29 | Deleting a user from the admin dashboard now erases their whole account — data, files, AI app sign-ins and login — the same way a user's own deletion does, and keeps the deletion record AMB-2808 |
| 5 | 2026-10-29 | The admin brand-identifier migration now only reports what it would change unless it is explicitly told to run, like every other admin data tool |
| 4 | 2026-10-29 | In the admin dashboard, Delete user now waits for the deletion to finish before it can be pressed again, so one click never starts two deletions |
| 3 | 2026-10-27 | The Dashboard opens for brand users, brand admins and superusers. The guide used to call the whole Admin section superuser-only AMB-2584 |
| 2 | 2026-06-08 | Reflect /admin/* namespacing + the superuser-only "Admin" sidebar section; "Admin Web" → "Web" (AMB-303) |
| 1 | 2026-03-01 | Initial guide |