Add a Complete Onboarding & Retention System

Scan my entire Base44 app first so you fully understand how it currently works before making changes.

Analyze existing app structure, pages, components, entities, roles, automations, backend functions, forms, navigation, and current user flows so anything you add fits naturally. Don't guess. Don't overwrite working logic unless required. Reuse patterns/entities/styling/permissions/architecture.

GOAL: Add a complete onboarding and retention system.

FIRST — Scan and document how the app works: all user roles; how new users are created; current signup/login/profile/first-use flow; entities/fields for users/accounts/plans/subscriptions/activity/status/engagement; backend functions/automations/email systems in place; the existing admin area (extend if possible); and the main "activation moment" — the key action a user must complete to get value. Based on the scan, design onboarding and retention around the ACTUAL purpose of the app.

FEATURES TO ADD:
A. GUIDED ONBOARDING FLOW — appears after signup/first login, multi-step, each step explains the next action, based on actual setup needs, allow skip, save progress, show progress, auto-complete based on user actions, don't force steps that don't apply to the role.
B. ADMIN VIEW OF ONBOARDING PROGRESS — admin dashboard section showing each user's status (complete/incomplete/skipped/stuck), filters by status/signup date/role/account type/progress, users who started but never finished, users who became active.
C. WELCOME EMAILS OR SEQUENCES — welcome email after signup, optional short sequence guiding toward completion, reuse existing email provider, store send history, prevent duplicates, admins see whether emails were sent.
D. SETUP CHECKLIST — visible checklist in a logical place reflecting the most important setup steps, auto-updates as users complete actions, shows completed + remaining, useful even after guided onboarding closes.
E. MISSING STEP REMINDERS — detect incomplete onboarding/critical setup, send reminders by email and/or in-app based on time delays + missing actions, don't send to users who completed required steps, give admins visibility into reminder status.
F. HEALTH SCORE / ENGAGEMENT TRACKING — a simple score based on real usage signals (onboarding completion, recent activity, feature usage, logins, setup completion), understandable, shown in admin with supporting reasons, scoring logic editable in code.
G. CHURN WARNING SIGNS — detect incomplete onboarding, low activity, inactivity, unfinished setup, declining usage, failure to reach activation; surface in admin so you can quickly identify users needing outreach and why they're at risk.
H. RE-ENGAGEMENT WORKFLOWS — identify inactive/stalled/at-risk users and trigger re-engagement emails, in-app prompts, or admin follow-up flags tied to what the user has/hasn't completed, with tracking of when actions triggered.

DATA AND STRUCTURE: Create missing entities/fields/relationships/backend functions/scheduled jobs/automations. Reuse existing user/account entities. Clean, normalized schema. Timestamps for onboarding started/completed, last active, reminder sent, engagement score updated, churn flagged, re-engagement triggered. Track status history. Admin-only permissions for internal progress/risk/retention data.

ADMIN AND PERMISSIONS: Use existing admin roles, plug into existing role logic, protect all admin onboarding/retention views, users only see their own data, internal notes/risk flags/operational views admin-only.

UI/UX: Consistent with current styling, no clutter, simple clear onboarding, useful (not overwhelming) admin reporting, good empty states/status labels/progress indicators, clear feedback after actions.

TECHNICAL: Existing Base44 patterns, reuse components, reuse email/notification/automation systems, don't break flows, don't remove working features, modular and maintainable.

TESTING: New user can sign up and go through onboarding; progress saves; checklist updates from actions; welcome emails and reminders trigger correctly with no duplicates; admin sees progress; health score updates from real activity; churn warnings flag the right users; re-engagement workflows trigger; permissions enforced; nothing broken.

FINAL OUTPUT: Summary of how the app works, what was added, new entities/fields/backend functions/automations/admin views, assumptions, areas needing manual review, and recommended next improvements.

IMPORTANT: Don't give generic onboarding. Tailor everything to the actual purpose and workflows of this app after scanning. Build as if it was in the app from day one.