> ## 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.

# Invite your team

> Add a colleague to your lab, choose their role and access tier, and set who verifies their results before release.

export const StillStuck = ({topic}) => <div className="ck-callout ck-callout--note" role="note">
    <p className="ck-callout__body">
      <strong>Still stuck{topic ? ` with ${topic}` : ''}?</strong>{' '}
      Check <a href="/platform/help/troubleshooting">Troubleshooting</a> first —
      it covers the failures we see most often. If that does not resolve it,{' '}
      <a href="/platform/help/contact-support">contact support</a> and include
      your workspace name and the time the problem happened, so we can find the
      matching entry in your audit log.
    </p>
  </div>;

export const TaskHeader = ({before, time, after}) => <div className="ck-task">
    {before ? <div className="ck-task__cell">
        <div className="ck-task__title">Before you start</div>
        <p className="ck-task__body">{before}</p>
      </div> : null}

    {time ? <div className="ck-task__cell">
        <div className="ck-task__title">Takes about</div>
        <p className="ck-task__body">{time}</p>
      </div> : null}

    {after ? <div className="ck-task__cell">
        <div className="ck-task__title">When you're done</div>
        <p className="ck-task__body">{after}</p>
      </div> : null}
  </div>;

export const Path = ({steps = []}) => <span className="ck-path">
    {steps.map((s, i) => <span key={i} className="ck-path__step">
        {i > 0 ? <span className="ck-path__sep" aria-hidden="true">
            ›
          </span> : null}
        {s}
      </span>)}
  </span>;

export const Availability = ({editions = ['all'], plans, roles, note}) => {
  const list = editions.includes('all') ? ['clinic', 'pharmacy', 'lims'] : editions;
  return <div className="ck-avail" role="note" aria-label="Feature availability">
      <span className="ck-avail__label">Available in</span>

      {list.map(e => <span key={e} className={`ck-pill ck-pill--${e}`}>
          {EDITION_LABELS[e] || e}
        </span>)}

      {plans ? <span className="ck-avail__label">Plan</span> : null}
      {plans ? <span className="ck-pill ck-pill--plan">{plans}</span> : null}

      {roles ? <span className="ck-avail__label">Who</span> : null}
      {roles ? <span className="ck-pill ck-pill--role">{roles}</span> : null}

      {note ? <span className="ck-avail__note">{note}</span> : null}
    </div>;
};

<Availability editions={['lims']} plans="All plans — seats are included up to your plan's cap" roles="Owner, Manager" />

Step 7 of the [setup checklist](/lims/get-started) — "Bring your team on board by inviting staff to your lab." The step completes only when a **second** person exists; as the owner you do not count as your own team.

<Path steps={['Settings', 'Staff & Teams']} />

<TaskHeader before="The person's name and work email, and a free seat on your plan" time="~1 minute" after="A colleague with an account, a role, an access tier and — if they need one — a named verifier" />

## Send the invitation

<Steps>
  <Step title="Open the staff list">
    Go to **Settings › Staff & Teams** ("Manage practitioners and roles"). The **Staff Members** card carries the **Invite Staff** button and shows **\{used} of \{limit} seats used**.
  </Step>

  <Step title="Enter their details">
    Select **Invite Staff**. The sheet is titled **Add team member** and runs through five steps — **Profile**, **Specialty**, **Supervisor**, **Permissions**, **Review**. The first is **Set up a profile** — "Enter the basic details for the new team member." Fill in **First name**, **Last name** and **Email**, then **Continue**.
  </Step>

  <Step title="Choose their role and access">
    **Choose roles for \{FirstName}** — "Select the specialty and access level for this team member." Pick the **Specialty** and the access tier. Both matter: the role decides which screens exist for them, the tier decides how much of the lab they can see.
  </Step>

  <Step title="Say who verifies their results">
    On the supervisor step — **Add \{name}'s laboratory credentials** — answer **Do \{name}'s results need verifying before release?** If yes, name a **Verifying scientist** ("Search for a lab director or verifying scientist..."). See the section below before you answer.
  </Step>

  <Step title="Set what they may do">
    On **Permissions**, grant the individual acts this person performs. Leave everything ungranted and they keep their role's defaults — enforcement is opt-in, not a wall you must build first.
  </Step>

  <Step title="Send it">
    Review, then select **Send invitation** (the button reads **Adding...**). The toast confirms **\{FirstName} has been added to your clinic** and they appear in the staff list.
  </Step>
</Steps>

## Roles a lab can assign

The specialty list is **Owner**, **Practice Manager**, **Lab Scientist**, **Radiologist**, **Radiology Technician**, **Phlebotomist**, **Doctor**, **Receptionist**, **Medical Biller**, **Accountant** and **Employee**.

Roles also limit which pages open at all. A **Lab Scientist** reaches the lab station, test requests, inventory and patients, but not Executive, Lab Analytics or Referral Commissions. A **Radiologist** sees imaging only. A **Phlebotomist** sees test requests, lab intake and patients. A **Receptionist** sees appointments, patients, test requests, imaging requests and billing.

Four administrative roles bundle a job rather than a screen:

| Role                   | Covers                                                                                                        |
| ---------------------- | ------------------------------------------------------------------------------------------------------------- |
| **Lab Manager**        | "Runs the lab: patient records, report release, test pricing and reports, staff accounts, announcements"      |
| **Accessioning Clerk** | "Front of house: registers patients, books collection slots, accessions incoming samples, raises the invoice" |
| **Referrer Liaison**   | "Looks after referring clinics: releases reports to them, handles their accounts and statements"              |
| **QC Officer**         | "Quality oversight: reviews QC runs, verified results and turnaround times. Read-only on patient records"     |

The QC Officer is review-only by design: quality inspects work rather than altering results.

## Access tiers

| Tier          | Sees                                                                                              | Gets                                                           |
| ------------- | ------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- |
| **Own bench** | "Sees only the samples and results on the bench they work"                                        | Result entry                                                   |
| **Whole lab** | "Sees every sample, result and patient at this site, across all benches"                          | Accessioning, rejection, result entry, verification, QC review |
| **All sites** | "Sees every collection site and bench, plus test pricing, referrer accounts and lab-wide reports" | Everything                                                     |

Individual acts can be granted on top: accession an incoming specimen, reject an unsuitable specimen, enter results at the bench, verify and authorise results, amend a verified result, review QC runs, configure analysers and interfaces, view turnaround-time analytics, access the referrer portal, and release a report to a referrer. See [Permissions](/platform/team/permissions).

## Supervision — the question that matters most

**Do \{name}'s results need verifying before release?** decides whether this person can sign work out. As the screen explains: a technician may run the sample and enter the reading, but the Lab Director — or another scientist qualified to verify — has to authorise the result before it can be reported, and is the only one who may amend it afterwards.

Verifiers can be lab scientists, doctors, radiologists or the owner. If nobody qualifies yet you will see "Nobody on the team is qualified to verify results yet. Invite a lab scientist or pathologist first, then come back and name them here." Invite the senior person first and the rest of the bench afterwards.

## Seats

Seats are included up to your plan's cap and nothing is billed per head. At the cap the invite is refused with **You've used all \{limit} seats on your plan.**, **Upgrade to \{NextTier} to add more team members.** and a **View plans** button; inside the sheet the same state shows **Staff Limit Reached**. See [Staff seats](/platform/plans/seats).

## Check it worked

* The person is listed under **Staff Members** and the seat count has moved.
* They can sign in and see the screens their role allows.
* The floating **Setup** checklist ticks **Invite a team member**.

## If something goes wrong

<AccordionGroup>
  <Accordion title="The invitation never arrived">
    Check the address on the staff list, then their spam folder. You can cancel a pending invite from **Pending Invitations** and send it again.
  </Accordion>

  <Accordion title="They cannot open a screen they need">
    That is the role, not a fault — role decides which pages exist. Change the specialty, or grant the specific act under permissions. See [Roles](/platform/team/roles).
  </Accordion>

  <Accordion title="They can enter results but not complete a test">
    They have "enter results at the bench" without "verify and authorise results", which is what supervision looks like when it is working. See [Enter and verify results](/lims/lab/results).
  </Accordion>

  <Accordion title="I have no verifying scientist to name">
    Invite one first. The supervisor step says so directly, and a technician invited without a verifier has nobody who can sign their work out.
  </Accordion>

  <Accordion title="The invite is refused at the seat cap">
    Every account counts on Diagnostics — there are no free roles. Upgrade, or remove a staff member who has left. See [Staff seats](/platform/plans/seats).
  </Accordion>
</AccordionGroup>

<StillStuck topic="team invitations" />