Workspaces and access
Organize studies, patient sessions and care teams with explicit access boundaries.
Start a study
- Configure matching API and browser Supabase settings, then sign in with a confirmed account.
- Create an empty research workspace and its first study. The creator receives an explicit coordinator role.
- Enroll a synthetic patient and create a draft session. Review clinician assignments and account links deliberately.
Who can see what?
| Role | Access boundary |
|---|---|
| Researcher | Identified records in their active studies. |
| Clinician | Currently assigned patients; multiple clinicians can be assigned concurrently. |
| Patient | Their own allowed records through a verified account link. |
| Organization administrator | Administration alone does not grant clinical records. |
Plans, messages and shared tools
Staff can author versioned protocols, assign pinned plans, manage devices and schedule encounters through declared actions. Invitations use private, email-bound codes accepted by the matching confirmed account.
Reading a clinical record does not grant membership in a private conversation. Patients may message authorized staff; patient-to-patient messaging is disabled. Sharing a module, protocol or dashboard never grants patient-data access.
Keep session history explicit
Session metadata supports draft, finalized and canceled states. Capture sealing and accepted analysis outputs have their own lifecycle. A finalized metadata record is not proof that a scientific analysis or clinical review occurred.
Commands use scoped retry identities. An interrupted response should be retried with the same identity; an intentional new operation needs a new one.