Organizations and members
An organization is the workspace. Members are the people who can manage that workspace.
Roles
| Role | What they can do |
|---|---|
| Owner | Everything. There is only one owner. Can transfer ownership and delete the organization. |
| Admin | Manage facilities, members, integrations, API keys, forms, concept sets, and doctors. |
| Member | Work inside allowed facilities. Can create and edit working resources like forms and doctor profiles. |
| Viewer | Read-only access inside allowed facilities. |
Facility access
Facility access answers this question:
Which facilities can this member see?
There are two modes:
| Mode | Meaning |
|---|---|
ALL | The member can access every facility in the organization. |
RESTRICTED | The member can access only selected facilities. If none are selected, they see no facilities. |
Owners and admins behave like ALL.
They are not limited by the restricted list.
Example
Imagine one organization with three facilities:
Madrid clinicBarcelona clinicValencia clinic
You can set:
| Member | Role | Facility scope | Result |
|---|---|---|---|
| Ana | Owner | ALL | Can manage everything |
| Luis | Admin | ALL | Can manage everything except ownership |
| Marta | Member | RESTRICTED: Madrid | Can work only in Madrid |
| Sofia | Viewer | RESTRICTED: Barcelona | Can only read Barcelona |
Important rules
- You cannot invite someone as
OWNER. - Ownership changes use ownership transfer.
- A member cannot change or remove their own membership from admin actions.
- Personal organizations are created automatically for users and are not managed like team organizations.
Member vs doctor profile
This is easy to confuse.
| Thing | What it means |
|---|---|
| Member | A human who can open the platform. |
| Doctor profile | The doctor identity used when creating consultations. |
A doctor can also be a member, but they do not have to be. For example, an API integration can create doctor profiles without giving every doctor platform access.