> ## Documentation Index
> Fetch the complete documentation index at: https://help.clinikehr.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Who can see and do what

> Four independent things decide what appears on your screen — your edition, your plan, your role and, in hospitals, your care areas.

"It's not on my screen" is the most common question we get, and it almost never has one answer. Four separate gates decide what you see, they are checked independently, and any one of them can hide a thing on its own.

## The four gates, in the order they are applied

<Steps>
  <Step title="Your edition — does this module exist here at all?">
    A pharmacy has no consultation screen. A diagnostic centre has no ward. This is decided by the kind of business your workspace is, it is fixed when the workspace is created, and no upgrade adds a module your edition does not have. See [The three editions](/start/editions).
  </Step>

  <Step title="Your plan — has this workspace paid for it?">
    Inside your edition, your subscription decides which capabilities are unlocked and how much capacity you get. A feature that is not on your plan usually still appears, as a locked card or an upgrade prompt, rather than vanishing. See [Change your plan](/platform/plans/change-plan).
  </Step>

  <Step title="Your role — may you open this page?">
    Your role in this workspace decides which pages your sidebar offers. An owner sees everything the edition and plan allow; a cashier sees the till; a phlebotomist sees intake. A page you have no role for is not in your navigation and cannot be reached by typing its address either. See [Roles](/platform/team/roles).
  </Step>

  <Step title="Your permissions — may you personally do this?">
    On a page you can open, individual permissions decide which actions you may take: refund a sale, discount an invoice, void a payment, see a profit figure. Two people with the same job title can differ here. See [Permissions](/platform/team/permissions).
  </Step>
</Steps>

Hospitals add a fifth filter on top: **care areas**, the statement of which departments the building actually runs. See [Care areas](/platform/team/care-areas).

## The gates are not the same thing, and they do not substitute

This is the part worth reading twice.

| Gate           | Answers                                 | Set by                         | Changes it          |
| -------------- | --------------------------------------- | ------------------------------ | ------------------- |
| **Edition**    | Does this module exist?                 | The kind of business you are   | Support only        |
| **Plan**       | Has this been paid for?                 | The subscription               | An owner, any time  |
| **Role**       | May this person open this page?         | The role on their staff record | An owner or manager |
| **Permission** | May this person perform this act?       | Per-person switches            | An owner or manager |
| **Care area**  | Does this hospital run this department? | Settings → **Facility**        | An owner or manager |

Upgrading a plan will never reveal a module your edition does not have. Giving someone a permission will never let them open a page their role excludes. Switching on a care area will never unlock a feature the plan does not include. They stack; they do not override each other.

## Why can't I see X?

Work down this table in order. The first row that matches is your answer.

| What you see                                                               | The gate       | What to do                                                                                                     |
| -------------------------------------------------------------------------- | -------------- | -------------------------------------------------------------------------------------------------------------- |
| The module is simply absent from the sidebar, and absent for the owner too | **Edition**    | It does not exist for your kind of business. [Compare the editions](/start/editions).                          |
| A hospital group (Theatre, Inpatient, Records) is missing for everyone     | **Care area**  | Switch the department on in Settings → **Facility**. See [Care areas](/platform/team/care-areas).              |
| The card is visible but locked, or you get an upgrade prompt               | **Plan**       | Ask an owner to [change the plan](/platform/plans/change-plan).                                                |
| The owner can see the page, you cannot, and it is not in your sidebar      | **Role**       | Ask an owner to review your [role](/platform/team/roles).                                                      |
| You can open the page, but a button is missing or greyed out               | **Permission** | Ask an owner to grant the [permission](/platform/team/permissions).                                            |
| A figure shows as **—** instead of a number                                | **Permission** | You may see the page but not that number. This is deliberate, not a bug.                                       |
| You are asked for a code before a patient record opens                     | **Two-factor** | Your workspace requires two-factor for patient data. See [Two-factor on patient data](/platform/security/mfa). |
| The whole workspace is missing after sign-in                               | **Workspace**  | You may be signed in to the wrong one. See [Switching workspaces](/platform/account/switching-workspaces).     |

## Figures degrade, actions refuse

The product treats seeing and doing differently, on purpose.

* **A number you may not see is hidden, not zeroed.** It renders as **—**. A blank is honest; a `0` would be a lie you could act on.
* **An action you may not take is refused, and the refusal is recorded.** You get a message saying so, and the attempt appears in the [audit log](/platform/security/audit-log) — which is what lets an owner tell the difference between "nobody tried" and "somebody was blocked".

## Owners and managers

Owners bypass the permission gate entirely inside their own workspace: they can perform every act their edition and plan allow. Managers sit just below them and can administer staff, roles and permissions.

Neither of them bypasses the edition gate, the plan gate, or the two-factor requirement on patient data. An owner who has not enrolled in two-factor in a workspace that requires it is blocked from patient records exactly like anyone else.

## Enforcement is opt-in

Per-person permissions only start applying to someone once an owner or manager has actually configured them. Until then that person is governed by their role alone, and nothing is silently denied. That is why a newly invited colleague can often do more than you expected — the fix is to set their permissions, not to change their role.

<Note>
  Adding staff has a cost or a cap depending on your edition: Clinic & Hospital bills each billable seat, while Pharmacy and Diagnostics include their seats and block the next invite when the cap is reached. See [Staff seats](/platform/plans/seats) before you invite.
</Note>

## Related

<Columns cols={2}>
  <Card title="Invite a staff member" icon="https://mintcdn.com/clinikehr/nLyvBRumcl1Yk8z3/images/icons/user-plus.svg?fit=max&auto=format&n=nLyvBRumcl1Yk8z3&q=85&s=a3fbf78fb687cbc78acbe559e500b46f" href="/platform/team/invite-staff" width="24" height="24" data-path="images/icons/user-plus.svg">
    Send an invitation, pick a job title and set the role.
  </Card>

  <Card title="Two-factor on patient data" icon="https://mintcdn.com/clinikehr/nLyvBRumcl1Yk8z3/images/icons/shield-halved.svg?fit=max&auto=format&n=nLyvBRumcl1Yk8z3&q=85&s=3d3f5c53a33441091182992bba0efd7f" href="/platform/security/mfa" width="24" height="24" data-path="images/icons/shield-halved.svg">
    Why a workspace can require a second factor before records open.
  </Card>
</Columns>