Admin Panel Production QA
Run these checks before deploying the admin panel or giving operational access to a team. The goal is to verify the dashboard, Firebase project, mobile app, roles, workflows, and production secrets together.
Technical Checks
From the admin panel directory:
corepack enable
corepack yarn install --immutable
corepack yarn typecheck
corepack yarn build
The production build should complete without TypeScript or Next.js errors.
Browser Checks
Open the dashboard and test:
- login and logout;
- Dashboard metrics;
- Launch Checklist;
- App Settings save;
- Admin Roles;
- Audit Log;
- Support user lookup;
- Media Library upload;
- CSV export;
- one safe create, update, and delete flow;
- one app-specific workflow page.
Test the dashboard at desktop width and at a narrow mobile width. The dashboard is primarily an operations tool, but support and moderation teams may still open it from smaller screens.
Firebase Checks
Confirm:
- Firebase Auth users exist in the expected project;
- Firestore reads and writes work;
- Firebase Storage upload works;
- public Firebase config and Admin SDK credentials point to the same project;
- service account credentials are server-only;
- no production build uses development smoke-test bypass values;
- Firestore and Storage rules are ready for the mobile app.
Role Checks
Create or verify one account for each role you plan to use:
| Role | QA check |
|---|---|
owner | Can access settings, roles, audit log, operations, support, campaigns, and entity pages. |
operator | Can run operational workflows without changing owner-level access. |
support | Can look up users and perform support actions without editing production settings. |
moderator | Can review moderation queues without accessing unrelated business settings. |
content_manager | Can manage content, media, templates, and campaigns where configured. |
Remove test accounts after QA unless they are part of the production team.
Mobile App Checks
Run the matching React Native app against the same Firebase project:
- sign in as a regular user;
- create or update a record from the mobile app;
- find the same record in the admin panel;
- update a safe field from the admin panel;
- confirm the mobile app reflects the update;
- verify push, payments, maps, chat, media, or other native features used by that app.
App-Specific QA
| App family | Required test |
|---|---|
| Commerce | Create product data, place an order, update status, verify mobile order state. |
| Food delivery | Create restaurant/menu data, place an order, verify fulfillment and driver readiness signals. |
| Appointments | Create provider/service data, create a booking, update booking status. |
| Taxi | Create car category and driver data, inspect a trip, verify status workflow and stuck-state recovery. |
| Listings | Create listing with image and coordinates, verify map/detail screens, test listing operation. |
| Social apps | Create content and a report, moderate it, verify visibility in the app. |
| Dating | Create complete profiles, report a user, review discovery/safety workflow. |
| Chat | Create a conversation, inspect it, mark reviewed or escalated. |
| GPT Chat | Create assistant conversation data, inspect support and usage signals. |
| Video Chat | Create or inspect AV call data, verify call status and connection data pages. |
Production Access Checklist
Before opening access beyond the setup team:
- rotate temporary credentials;
- remove temporary owner accounts;
- keep at least two owner accounts;
- verify HTTPS hosting;
- confirm support and legal links;
- confirm sender identity for email campaigns;
- confirm push notification platform setup;
- review Audit Log after the first operational actions.