System Actors
The roles in Medisa and what each of them can do.
Medisa is used by several kinds of people with different needs. This page sets out who they are and what each can do, so you know which guide pages apply to you.
Two workspaces
Before the roles, one concept shapes everything else: every doctor always has a personal workspace, and can additionally belong to one or more organizations.
What decides the working context is the workspace that is active when you record:
- In the personal workspace, records belong to you and quota comes from your own subscription.
- Inside an organization, records are attached to that clinic and quota comes from the seat assigned to you.
Check the active workspace before recording
Switching clinics changes the data you see and the quota you spend. If a patient list looks empty or the quota is not what you expected, the first thing to check is which workspace is active.
User roles
Doctor
DoctorMedisa's core user. Records consultations, reviews and edits SOAP notes, manages patient data, and replays audio.
A doctor can work entirely alone on a personal subscription, or belong to a clinic. The clinical capabilities are identical either way; what differs is where the quota comes from and who else can see the data.
Organization Owner
Organization OwnerThe person who created the organization — usually the clinic's owner or the person accountable for it. Holds every admin capability, plus control over billing and over the organization itself.
An owner also occupies a seat if they practise.
Clinic Admin
Clinic AdminThe day-to-day team manager, for example a clinic manager or senior doctor. Buys and assigns seats, invites and removes members, sets roles, and monitors usage.
Being an admin does not automatically grant sight of other doctors' records — data access follows the organization's sharing settings, not the job title.
Developer
DeveloperA third-party integrator connecting another system to Medisa through the API. Works with an API key rather than a doctor account, and their usage is metered separately.
Medisa Admin
Medisa AdminMedisa's internal staff. Manages accounts, plans, vouchers, languages, and organizations from an internal dashboard. This role is not used by customers and is not covered in this documentation.
Patient
A patient is the subject of a medical record, not a user of the app. Patients do not sign in and have no account; their data is managed by the treating doctor.
Referral partner
A user enrolled in the partner program who earns commission on the subscriptions they introduce. The role sits on top of an existing account — a doctor can also be a referral partner.
Capability summary
| Doctor | Clinic Admin | Organization Owner | Developer | |
|---|---|---|---|---|
| Record and create an EMR | ✅ | ✅ | ✅ | via API |
| Edit their own EMR | ✅ | ✅ | ✅ | — |
| Manage patients | ✅ | ✅ | ✅ | via API |
| Create an organization | ✅ | — | ✅ | — |
| Invite and remove members | — | ✅ | ✅ | — |
| Buy and assign seats | — | ✅ | ✅ | — |
| Set member roles | — | ✅ | ✅ | — |
| See team usage | — | ✅ | ✅ | — |
| Manage organization billing | — | — | ✅ | — |
| Delete or transfer the organization | — | — | ✅ | — |
| Call the API with an API key | — | — | — | ✅ |
Clinic Admins and Organization Owners each occupy a seat too if they practise — a title does not exempt anyone from the seat count.
Related pages
- Organization Feature — the detail of who can see what
- Creating an Organization
- Adding Organization Seats