Read-only preview

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.

Platform settings & site content

Global flags and public marketing content — read-only previews.

Platform flags (sample)

  • Maintenance mode — Off (sample) — Off (sample)
  • Internal preview host — CCS private preview (hosted URL in OWNER-PORTAL-5 doc) — CCS private preview (hosted URL in OWNER-PORTAL-5 doc)
  • Customer workspace guard — Separate from portal — Separate from portal

Public site preview

Read-only CMS preview for homepage, pricing, FAQ, and marketing copy — sample data only.

Marketing pages preview · no live editing

Open CMS preview →

Public site content (read-only CMS preview)

Marketing copy is illustrated in the owner portal CMS preview section. Public pages on this host remain static PHP shells — nothing is written to disk or database from the portal.

  • Homepage hero — Static shell in index.php
  • Demo page — Live preview route at /demo/
  • Pricing / FAQ / contact — Routes not rebuilt yet — cards only
  • Full CMS preview — Open Public site content in sidebar

Read-only content preview — no CMS forms and no live content changes from this host.

Open CMS preview →

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.

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.

Back to portal overview

Back to portal overview ← Public homepage