Prototype Dev simulation only. No real authentication, no production data, no live PHI. Pick a role to walk the workflow.  ·  Back to commercial site

Dev preview · simulated

Pick a role to walk the substrate.

This is a simulated sign-in for the JoyPartnersOS dev prototype. None of these flows wire to a real backend. There is no password to type, no token to issue, and no PHI to render. Each card opens the corresponding portal mockup as a static walk-through.

Every action inside these portals is a static walk-through. No data is written, no API is called, no credential is exchanged.

Production posture (future gate)

What a real sign-in will look like, when authorized.

The real JoyPartnersOS auth surface is a separately authorized future implementation lane. It will use email-verified provider / CHW / referral-partner identities, an admin-approval registration workflow, role-based access control, and an audited, dev-only impersonation pattern (never a production "super admin bypass" of login). Until then, this prototype shows the workflow only.

  • Registration lifecycle: requested → email_verified → pending_admin_review → approved | rejected | needs_changes → active | suspended | deleted.
  • Roles: super_dev_admin · super_admin · provider_user · chw_user · biller_user · beta_applicant.
  • Super admin bypass: explicitly prohibited. The safe pattern is super_dev_admin authenticates normally then uses a dev-only audited impersonation control under a separately authorized non-production gate.
  • Audit: every state transition emits a ledger-tagged audit record. PHI stays under custody; downstream metadata is minimized.

Compliance-safe disclaimer

Sign-in shown here is a non-functional UI prototype. No HIPAA, FDA, SOC2, HITRUST, or reimbursement certification claim. No autonomous clinical, billing, payroll, or legal decisioning. Synthetic identifiers only on every portal page.