EmberDeck AppStart Guide (Zero to Hero)
Target web URL: https://emberdeck.xyz/appstart
This guide is for a brand-new user going from first launch to confidently using EmberDeck with Firebase projects.
1) What you will finish
By the end, you will:
- Sign in and complete onboarding.
- Connect to at least one Firebase/Google Cloud project.
- Confirm read access works for your key services.
- Configure write safety (lock/unlock flow).
- Validate Events automations and run logs.
- Know where to troubleshoot quickly.
2) Before you start
You need:
- A Google account with access to at least one Firebase project.
- Permission to view project resources (minimum: read-level for target services).
- Internet access from your device.
Recommended:
- Owner/Editor access for setup, then reduce to least privilege.
- A dedicated app account identity for production use.
3) First launch and sign-in
- Open EmberDeck and sign in with Google.
- Complete onboarding.
- Confirm you land on Projects (
/home/projects). - Select a project.
Verify success:
- The top safety banner shows the active project.
- You can open the selected project details without auth errors.
4) Confirm core project access
From the left rail or bottom nav, open these in order:
- Firestore:
/home/firestore - Realtime DB:
/home/realtime-db - Storage:
/home/storage - Auth Users:
/home/auth
Verify success:
- Each screen loads (data grid/list or clean empty state).
- No repeated permission-denied loops.
- Project context remains the same in the safety banner.
If access fails:
- Use Projects -> Update Permissions.
- Re-test the same screen.
5) Write safety model (important)
EmberDeck is read-first.
- Locked mode: browse safely.
- Unlocked mode: allows guarded writes where supported.
Steps:
- Keep project locked for normal browsing.
- Unlock only when needed for write actions.
- Re-lock after finishing changes.
Verify success:
- Lock state changes visibly in app bar/safety banner.
- Write actions are disabled when locked and enabled only when unlocked.
6) Events/Automation setup quick path
Route: /home/events
Steps:
- Create an automation (or open existing).
- Ensure service account/app account linkage is valid.
- Set schedule and save.
- Open automation details.
- Review recent run attempts and statuses.
Verify success:
- Automation row appears in Events list.
- Last run timestamp/status updates after run-now or schedule.
- Run attempt history appears in event details (latest 100 + load more).
7) Messaging/Results and Audit checks
Routes:
- Messages/Results:
/home/events-messages - Audit:
/home/audit
Verify success:
- Messages/Results screen opens and filters/responds.
- Audit entries appear for major operations.
8) Connection and trust checks
Routes:
- Connection diagnostics:
/home/connection-diagnostics - Legal/trust:
/home/legal-trust
Use connection diagnostics when data does not load or seems delayed.
9) First-day validation checklist
Use this exact checklist:
- Signed in and onboarding complete.
- Active project selected and shown in safety banner.
- Firestore/RTDB/Storage/Auth screens all open successfully.
- Lock/unlock behavior validated.
- At least one automation created or viewed.
- Automation run status/history visible.
- Messages/Results opens.
- Audit entries visible.
- Connection diagnostics runs successfully.
10) Where to get help
In app:
- Help button in top app bar opens this guide.
- Get help now screen (
/home/support) for direct support/community links.
If something is broken:
- Capture exact screen + action + timestamp.
- Include error text/snippet.
- Include project ID (if safe to share).
11) Suggested follow-up pages (same guide family)
Create additional web pages from this source set:
/appstart/permissions-> IAM roles and least-privilege setup./appstart/events-> automation setup + run interpretation./appstart/troubleshooting-> common failures and fixes./appstart/security-> lock/unlock and safe operating model./appstart/faq-> short answers for common onboarding questions.