Patient authentication in the RPM app

Ovok Care signs in existing Patient accounts in one configured tenant. It does not create a project, administer settings, or provide a registration screen. A Console administrator account cannot be used as the app's Patient session.

Configuration boundary

The app's environment supplies a public API origin and tenant code. The project administrator separately enables patient sign-in and assigns appropriate patient-scoped permissions. The tenant code identifies the project; it is not a credential.

The app prompts for Patient email and password and continues with a verification code when MFA is required. Do not place client secrets, administrator credentials, Patient passwords, or access tokens in the app's source or EXPO_PUBLIC_ settings.

See Connect a sandbox project for the complete Console and local environment setup, and Ovok authentication for the platform contract.

Explore the source: Settings.tsx implements sign-in and MFA continuation; ovok.ts creates the shared client with the configured tenant and API origin.