Skip to main content
A role answers one question: which pages does this person get? What they may do on those pages is a separate setting — see Permissions. Roles come in two halves, and someone can hold both. A clinical role says what they are professionally — the Specialty you pick when you invite them. An administrative role says what they run. Alongside it sits an access tier, which says how far their view reaches.

Owners and managers

Owners bypass the permission system entirely inside their own workspace: they can perform every act their edition and plan allow. Managers also bypass it, but they do not inherit the owner’s administration screens — inviting a colleague, changing a specialty and editing permissions are all on the owner-only Actions menu of Staff Members. Both are deliberately absent from the role-based navigation controls further down this page. There is no configuration that hides a page from an owner, and that is intentional — somebody has to be able to see everything. Neither bypasses the edition gate, the plan gate, or a workspace’s two-factor requirement on patient data.

The roles, by edition

Administrative rolesAccess tiersBiller and scheduler seats cost nothing and count toward no cap — as long as that person is not also clinical. See Staff seats.Physician Assistant is a clinical specialty (title PA-C) with the same access as a Nurse Practitioner: it can prescribe, write and sign notes, and is reached by emergency alerts. It takes a paid seat, like any clinician. It is a clinical role you pick as the Specialty, not an administrative role.Technical roles — Developer, IT Admin and CTO — are for the people who connect and look after your systems. See Technical roles below.

Technical roles

Developer, IT Admin and CTO are for the person who connects your clinic to other software and keeps it secure. They never see patient information. On every Settings page except API access, a technical role sees the values but cannot change them: fields are greyed out, the buttons that save, add, edit or delete are not shown, and a line at the top says You can view these settings. An owner or manager can change them. On API access a Developer or CTO can create and revoke keys; an IT Admin sees a view-only message until you grant Manage API access. A technical role lands on Settings after sign-in and sees nothing else in the sidebar. If they open a link to any other page, they see a screen saying their role does not include it. This is not a setting you can switch off: it applies on every plan, and it is also enforced where your data is stored, not only in the menus. Creating a live API key still asks for a second factor, exactly as for an owner. See API access. On Clinic & Hospital the three technical roles are free seats. On Pharmacy and Diagnostics every account still counts toward the plan’s cap, technical roles included.

Where a role lands after sign-in

ClinikEHR puts people where their work is rather than on a generic dashboard. A cashier opens on the till; a phlebotomist opens on intake. You do not configure this on most plans — it follows from the role.

Role Navigation

Hospitals can go further and state, per role, which parts of the building appear in the sidebar at all.
1

Turn the master switch on

The Role-based navigation card — “Show each staff member only the parts of the hospital their role works in.” — carries the switch Scope navigation by role. With it on, “a governed role sees only its own menus, is returned to its own area if it opens a direct link elsewhere, and lands there after signing in.”Leave it off while you set the rules up. The editor below says so: “Role-scoped navigation is switched off, so these rules are not being applied yet.”
2

Tick the modules each role may open

The Role navigation card lists each role with the sidebar sections underneath. Tick what that role works in.
3

Save

Save stores that role’s list; Reset to default puts it back. A role you have customised is badged Custom; one you have not is badged default.
Two things about this screen are worth knowing before you use it. The first ticked module becomes the landing page. The helper text under each role says which — “Lands on Front Desk after sign-in.” — and if you tick nothing it tells you “Choose at least one section — the first becomes where this role lands.” Order matters, so put the section they should open on first. The toggles work at the level the rule works at. Switching off Insurance necessarily covers the insurance dashboard, pre-authorization and claims together, because they are one part of the building rather than three. You cannot grant one and withhold another from here — use Permissions for that finer cut.
This is navigation, not security. The card is explicit: “This changes navigation only — it is not a security control. What each person may read and write is still decided by their permissions.” Owners, managers and clinicians are never restricted by it, and Settings and the audit log stay reachable for every role whatever you choose. Changes reach signed-in staff within five minutes.

Changing someone’s role

From the row menu on Staff Members, Change Specialty updates the specialty for an existing member. Their administrative role and permissions are managed from the same menu under Permissions. Changing a role or permissions needs a session that has just passed your second factor; if it has not, you are asked to verify first. See Actions that always ask for your second factor.
The full row menu is the owner’s. An accountant can open Settings → Staff & Teams and read the list. A manager gets a shorter row menu and can deactivate team members who are not managers, but never another manager or themselves. Permissions and Invite Staff are the owner’s.

Permissions

What an individual may do on the pages their role already opens.

Invite someone to your team

Pick the role in the first place.

Care areas

Which departments exist at all, before any role sees them.

Who can see and do what

Which of the four gates is hiding your page.