Role-Based Access Control Explained
A conceptual look at how roles and permissions scope what each user can see and do across USystems Atlas.
USystems Atlas controls what a user can see and do through role-based access control, or RBAC. Instead of granting permissions to individuals one by one, you assign each user a role, and that role determines their access across the whole platform.
Out of the box, the platform ships with several common roles. Front-desk staff can register patients and manage appointments but cannot view billing history. Clinicians can read and update clinical records for patients under their care but have limited visibility into administrative settings. Billing admins can create and adjust invoices and view payment history but cannot alter clinical notes. Super-admins can manage users, roles, and tenant-wide configuration.
Permissions are scoped, not just categorical — a clinician role, for example, typically only grants access to patients within their own department or facility, not the entire tenant. This scoping is what keeps a large hospital's data need-to-know even when many people work inside the same system.
Administrators can create custom roles under Administration > Roles by combining specific permissions, which is useful when the built-in roles don't quite match how your organization is structured.
Was this helpful?