Users
5Platform and tenant users.
native admin dashboard
Platform Admin
What needs attention
Platform and tenant users.
Owner, facility, and service groups.
Neutral asset model with demo labels.
Relationship request states.
Permission vocabulary for selected role.
Seed entries plus simulator events.
Geographic overview
State is the first geographic layer for admin growth tracking and future service discovery. Larger states can add region or metro labels later; county-level organization is not needed yet.
Search/index concept
This is an index concept only. It does not perform live search, use real location services, or expose production customer data.
Role Dashboard Switcher
Platform Admin can preview each role dashboard in mock mode. Normal mock users only see dashboards attached to their selected role/context cards. This does not create separate production accounts or change the base user/person model.
Platform admin can preview every dashboard/user context in mock mode.
Client-only user sees only the owner/client dashboard.
Client + Barn user sees owner/client and facility/barn contexts.
Client + Trainer user sees owner/client and trainer contexts.
Multi-role user sees only attached contexts, not the platform admin dashboard.
Native admin dashboard for tenant oversight, diagnostics, forms, and audit context.
Preview owner/client assets, relationships, handshakes, records, assigned tasks, and calendar.
Preview facility/barn connected assets, handshakes, location settings, chores, and facility calendar.
Preview trainer clients/assets, program templates, Step Detail Builder, homework, and schedule.
Preview professional visits, authored records, retained access, follow-up care, and service profile placeholders.
Product Architecture Status
Owner overview, tasks, calendar, records, and relationship examples are visible.
Facility workflow sections are now built from the mock provider.
Trainer workflow sections, program templates, structured step builder, homework, calendar, records, and next-step flow are built from the mock provider.
Professional workflow sections, visits, authored records, follow-up care, retained access, coordination, and service profile placeholders are built from the mock provider.
Platform Admin can preview all role dashboard contexts; normal mock users see only attached dashboards.
Sidebar menu labels change by active role context while keeping attached dashboards accessible.
Core navigation, overview, forms, handshakes, diagnostics, and role shells remain active.
Core tables, fake/demo seed data, and auth_user_id mapping exist in Supabase.
Main dashboard/forms/actions still use the mock provider.
Limited test RLS migration exists but remains unapplied.
No EquineSteps.com connector exists yet.
Create/update actions mutate local React/mock state and audit entries only.
Typed model, structured step detail builder, trainer homework, facility tasks, and professional follow-up context exist; database tables are draft-only.
Typed model and mock context exist; database tables are draft-only.
State, city, region, and service-area hints exist in mock data only.
No applied tables for assignments, templates, structured step details, or completion state.
No applied tables for events, attendees, visibility, or event links.
No applied location columns for users, organizations, assets, or discovery profiles.