Read-only preview. No live provider records are shown.
Platform owner portal
Separate trust boundary from customer organisation workspaces (/app/). Manage fictional customer setup previews only — not day-to-day care records.
Owner portal preview — No live customer data, no billing, no user invites, and no database writes. Platform owner read-only shell for future customer setup workflows. Read-only portal shell
Platform portal authentication is not implemented yet.
Structured guard only — no header redirect in DEV-BUILD-4.
Preview only. No portal login POST, no admin session from a form, no database queries, no customer workspace access, and no billing or email integrations.
Customer setup workflow (read-only preview)
Per-organisation setup panels, go-live checklist, and queue — fictional data only. No customer records written.
Customer management safety (read-only)
No live customers on this host
No database writes from the portal
No billing or payment processing
No invite emails sent
No workspace activation or live tenants
No customer data access from portal screens
No app impersonation or login-as-customer paths
Portal is separate from /app/ customer workspace guard and uses fictional sample data only.
Oakview Care
oakview-care
setup_in_progress
Setup stageModule selection
Lead / sourceSales handoff (fictional) — inbound register shell reference
Modules requestedSupport Plans, Incidents, MAR / Medicines, Learning Hub
Branding checkedColours and workspace label — preview only
Users invitedNo email sent on this host
Demo reviewedCCS /app demo journey separate from portal
Go-live gateNot active — no workspace live transition
Workspace liveFuture state — no customer created here
Customer workspace URLs (preview explanation)
Customers do not need separate cPanel subdomains by default. Future customer workspaces should use organisation slugs and tenant-scoped settings on the same codebase rather than separate copied sites.
Illustrative slug oakview-care
Future path pattern /workspace/{slug}/ (not routed on preview host)
Current preview /app/ with demo or customer session (separate from portal)
Tenant model Same codebase — organisation settings scoped after auth (future)
Future customer workspaces should use organisation slugs and tenant-scoped settings rather than separate copied sites. This preview does not create routes, subdomains, or live tenants. Branding can be stored per organisation later — no routing or .htaccess changes in this pack.