Roles, Permissions, and Access Control
ClinicOS lets you define exactly what each team member can see and do:
Written By Brendan Baker
Last updated About 7 hours ago
Every role can be customized, and each permission is governed through MCP, ensuring safe, consistent access across devices, users, and locations.
Whether youβre a single clinic or a multi-location group, permissions stay synchronized, predictable, and easy to manage.
Default Roles
PawthosX includes five preconfigured roles commonly used in veterinary operations:
DVM (Doctor)
CSR (Client Service Representative)
VA (Vet Assistant / Technician)
Manager
Inventory Manager (VA + Supply Room)
Admin (full system access)
Enterprise names can be added with permission levels.
These roles can be customized, expanded, or replaced based on your teamβs needs.
How to Edit Roles
You can assign and adjust access at any time.
1. Go to (as admin):
Settings β Globalβ Team & Access
2. Choose:
Select an existing team member
Or invite a new staff member
3. Set permissions:
Assign a base role
Adjust individual module access
Select access level (local-only or cloud-linked)
Access Levels
Each permission can be tied to a location, device, or cloud identity.
Local-Only
Access tied to a clinicβs local device or terminal
Ideal for assistants or CSR stations
Limits sensitive content outside the building
Cloud-Linked
Access follows the user across devices and locations
Ideal for DVMs, Managers, Admins
Enables multi-site continuity and secure off-site review
MCP enforces these access rules in real time.
Module Permissions
Updated with Atlas replacing RoomOps.
(Additional module lines can be added as new features go live.)
How Permissions Work Across the System
Permissions arenβt just βon/off.β
They shape the entire experience:
TriageAI: all clinical staff may triage; CSR access surfaces fewer internal details
DischargeAI: DVM + VA can author; CSR can send if allowed
InventoryOps: CSR + VA handle daily tasks; DVMs see controlled logs; managers supervise
Atlas & Flowboard: all clinical roles have access to routing, timers, statuses
PulseCheck: operations-level visibility for managers/admins only
VetVault: controlled repository; access varies by compliance settings
Every permission is watched by MCP to prevent cross-role leakage.
FAQ
Can I disable a module for an entire role?
Yes.
Go to Admin β Team & Access β Roles and toggle modules individually.
Can I create custom roles?
Yes β full flexibility is supported in the global release.
Examples:
Surgery Tech
Oncology DVM
Lead CSR
Inventory Manager
Medical Director
Do permissions sync across locations?
If the user is cloud-linked: Yes.
If local-only: access stays restricted to that clinic.
Can roles restrict which alerts a user receives?
Yes β alert visibility is controlled per role under Alerts β Role Filters.