Invite staff and give each person exactly the access they need.

app.chartling.io C Chartling GETTING STARTED Quick start PATIENTS & CLIENTS Patients Clients CLINICAL Visits & SOAP AI scribe Medications & Rx Controlled subs. Lab orders Discharge & comms AI FEATURES Clinic Copilot Clinical support SCHEDULING Appointments BILLING Invoicing & pmts SERVICE MODULES Boarding Daycare Grooming Training TEAM & SETTINGS Team & permissions Clinic settings SMS & reminders Audit log Docs โ€บ Chartling โ€บ Team & permissions Team & permissions NAME PERMISSION PACK STATUS SC Dr. Sarah Chen sarah@vetclinic.com Owner-admin Active JP James Park, DVM jpark@vetclinic.com Vet Active MT Maya Thompson, RVT mthompson@vetclinic.com Vet tech Active + Invite user
  1. Go to Settings โ†’ Team & permissions and click Invite by email

    Enter the staff member's email address.

  2. Select a permission pack

    Choose the pack that matches their role. See the Permission packs table below.

  3. Set an access expiry date (optional)

    For a temporary or relief vet, set a date their access expires automatically. That suits a locum engagement with a known end date. Leave it blank for ongoing staff.

  4. Send the invite

    The invitee receives an email with a setup link, valid for 14 days. They create their account and are immediately linked to your clinic. If they miss the window, resend the invite from their row in the team list. Resending refreshes the link for another 14 days.

Invites are tied to your clinic

When someone accepts an invite, their account is linked to your clinic organization. They won't be able to access any other clinic's data.

Permission packs

Chartling uses permission packs instead of fixed roles. A pack is a curated set of permissions appropriate for a type of staff member. You choose a pack when inviting; you can adjust it later.

Pack Who it's for Key capabilities
Vet Licensed DVMs Sign SOAP notes, prescribe, dispense & witness controlled substances, full patient record access
Associate Vet Associate or new-grad DVMs Same as Vet: sign SOAPs, prescribe, dispense & witness controlled substances
Vet Tech Credentialed vet technicians Record vitals, run labs, treatment execution, witness controlled substance dispenses
Senior Tech Lead or senior technicians All Vet Tech capabilities plus witness and reconcile controlled substances
Receptionist Front desk, client service Scheduling, check-in, invoicing, client communications
Practice Manager Non-clinical managers Reports, billing read, inventory operations, audit log view
Owner / Admin Clinic owners, senior managers Full access including all controlled substance permissions, team management, and billing
Read-only Auditor External reviewers, compliance staff View-only access to clinical and billing records, with no write access
Locum Temporary or relief vets Same as Associate Vet: sign SOAPs, prescribe, dispense & witness controlled substances, minus the ability to void a sent invoice

Controlled substance permissions

Several default packs include controlled substance permissions. The Vet, Associate Vet, and Locum packs include rx.controlled.dispense and rx.controlled.witness. The Vet Tech pack includes rx.controlled.witness. The Senior Tech pack includes rx.controlled.witness and rx.controlled.reconcile. The Owner / Admin pack includes all three. Other packs (Receptionist, Practice Manager, Read-only Auditor) have no controlled substance access by default. Chartling grants permissions through packs, not per-user checkboxes. To give one person controlled substance access, an Admin either assigns them a pack that already includes it, or creates a custom pack with exactly the permissions needed (rx.controlled.dispense, rx.controlled.witness, and/or rx.controlled.reconcile) under Settings โ†’ Team & permissions โ†’ Permissions and assigns that pack to them.

Locum carries controlled-substance access by default

Because Locum is seeded from the same permission set as Associate Vet, a relief or temporary vet can dispense and witness controlled substances from day one, before you've reviewed their pack. If your clinic wants a relief vet to earn that access separately, clone Locum into a custom pack with rx.controlled.dispense / rx.controlled.witness removed and assign that instead.

Vet Tech's rx.controlled.witness isn't reachable on its own today

The Vet Tech pack holds rx.controlled.witness, but the only screen that acts on it (Inventory → Controlled log) is itself gated on rx.controlled.reconcile, which Vet Tech doesn't hold. In practice, only Senior Tech, Owner/Admin, or a custom pack with both permissions can complete a witness through the app right now. See Controlled substances for the full explanation. If you need a Vet Tech witnessing independently, add rx.controlled.reconcile to their pack (or a custom one) in the meantime.

PermissionWhat it allows
rx.controlled.dispenseDispense a controlled substance to a patient
rx.controlled.witnessWitness a controlled substance dispense (must be a different user from the dispenser)
rx.controlled.reconcileRun and sign off on the controlled substance reconciliation report

Seat counts

On Intelligence and Practice, only licensed-veterinarian seats are billed per-vet. Techs, assistants, and front desk are unlimited free seats on every paid tier. Adding a vet increases your subscription; you'll see the prorated charge on your next invoice. Your current seat count is visible in Settings โ†’ Plan & subscription.

Staff schedule & time clock

Staff schedule and Time clock are separate sidebar pages (Operations and Practice tiers, feature scheduling). The schedule is a planned roster of shifts; the time clock is what staff actually clocked. They're deliberately different artifacts, so the schedule doesn't silently become the payroll record.

Customizing permissions

Chartling grants access through packs, not per-user checkboxes. There's no individual override screen on a staff member's profile. To give someone access outside their current pack, either move them to a different existing pack, or go to Settings โ†’ Team & permissions โ†’ Permissions and create a custom pack with exactly the permissions you need (you can clone an existing pack as a starting point), then assign that pack to them. Changes take effect immediately. The user doesn't need to log out.

Removing access

To remove a staff member, go to Settings โ†’ Team & permissions, find their row, and deactivate their account. Deactivated users can't log in. Their records (SOAP notes they signed, actions they took) are preserved. Removing a user does not alter the audit trail.

Transfer any unsigned visits or pending items before deactivating. Unsigned visits are visible under Visits โ†’ Unsigned.

FAQ

What's the difference between packs and roles?

Traditional role-based systems give a user a single role with a fixed permission set. Chartling's packs work the same way (Vet, Vet Tech, Receptionist, etc.) but they're fully editable: clone any pack, add or remove individual permissions, and save it as a custom pack. There's no per-user permission override on top of a pack. If one person needs a different set of permissions than everyone else on their pack, give them their own custom pack.

Can I have a vet with no billing access?

Yes. Clone the Vet pack under Settings โ†’ Team & permissions โ†’ Permissions, uncheck the billing-related permissions, save it as a new pack (e.g. "Vet, no billing"), and assign that pack to them instead of the standard Vet pack.

What happens to a staff member's records when they're deactivated?

Their signed SOAP notes, dispense records, and audit log entries are all preserved permanently. Deactivation only prevents future logins. It does not alter historical records.

Can a staff member belong to two clinics?

Yes. The same login can be a member of more than one clinic organization and switch between them from the workspace menu at the top of the sidebar. Permissions are set separately per clinic, so a pack assigned in one org has no effect in the other. Separately, on the Practice tier, a multi-location group can also link its clinics into a network (Settings โ†’ Network) for cross-site referrals and aggregate rollups. That's org-to-org linking, not a shared staff login.

Something missing? We're always improving these docs.

Contact support Open app