Roles and Access
ClaimPod has four roles. Which one you hold decides what appears in your sidebar, and the split is not the usual “administrators see everything”.
| Role | What it is for |
|---|---|
| User | The billing work. Patients, visits, claims, remittances, queues. |
| Manager | Workload distribution: queues, assignments, reporting. |
| Administrator | Configuring ClaimPod: users, clients, rules, imports, reference data. |
| Superadmin | Everything, including the access logs. |
Administrators Cannot See Patient Data
Section titled “Administrators Cannot See Patient Data”This surprises people, so it is worth stating plainly: an Administrator has no Patients page, no Visits, no Claims and no Remittances. Not hidden behind a warning, not read-only. Absent.
That is deliberate. Someone has to manage accounts, rules and imports, and that job does not require seeing anyone’s medical record. Keeping the two apart means the person with the most configuration power has the least exposure to protected health information, and the audit trail stays meaningful rather than recording that the administrator opened everything.
The practical consequence: the person who sets ClaimPod up cannot test the billing screens. Whoever does that work needs the User role as well.
What Managers See
Section titled “What Managers See”A Manager gets the queues, assignments, analytics and the client list, but no patient-level screens either. It is a coordination role: deciding who works what, not working it.
Access Is Granted Per Client
Section titled “Access Is Granted Per Client”Your role says what kind of thing you can do. Client access says which practices you can do it to, and it is granted per user. Holding the User role grants nothing on its own until an administrator adds you to a client.
If you sign in and see a no-client-access notice, that is what happened: the account exists, the grant does not.