Patients
Already invited or provisioned
Patients with existing access should return to the protected patient portal and continue their current work there.
Public patient self-signup is not available from this route.
Signup
Access starts through the right workflow
Klark does not collect public registration details here. Patients and clinicians continue through existing access, organisation setup, or invite-led onboarding.
- No public registration form
- Invite-led clinician access
- Existing patient route
Access path
Three access situations, three clear next steps
A healthcare workflow should not ask people to guess where account creation begins. This page keeps the decision simple.
Clinicians
Organisation-led access
Clinicians continue through the existing dashboard when access is already provisioned or an invite has been accepted.
Open clinician self-signup is intentionally not part of the public front door.
Teams
New rollout conversation
Teams evaluating Klark should start with a workflow and onboarding discussion before new access is provisioned.
Workflow
Access follows clinical workflow context
The access model keeps patient work, clinician review, and organisation setup attached to a known context.
-
Organisation context
Access starts from a care team, organisation, or existing product relationship.
-
Role selected
Patient and clinician paths stay separate before protected workflows begin.
-
Protected sign-in
Authentication happens inside the existing patient or clinician product surface.
-
Workflow continues
Users return to intake, review, or access management without public data capture.
Trust
Why there is no open signup form
The absence of a public form is an intentional trust boundary, not a missing marketing feature.
Clarity
No clinical data at the public edge
This page gives route guidance only. Clinical or account data belongs in protected product surfaces.
Oversight
Clinician access is controlled
Clinician onboarding remains tied to organisation membership and invite workflows.
Continuity
Existing users resume work
Patients and clinicians go back to the product area that already holds their workflow context.
Responsibility
New access needs review
New team access is best handled with onboarding, governance, and rollout context agreed first.
Current State
No registration data is submitted here
The route exists to make access expectations clear while account creation remains inside existing product and organisation workflows.