Practice ops
Roles & permissions
Four roles that match how billing companies actually work. Admin, Supervisor, Biller and Accountant. Each sees what their job needs and nothing more. When everyone is an admin, nobody is accountable. What ships here includes admin: full ops plus the admin console; supervisor: full ops, limited user creation. Used day to day by admin roles, with availability marked available. Open the sample screen on the right, then walk the steps below — or book a demo and put your hand on the same flow with synthetic data.
Admin console · users & practices
| User | Role | Practices | 2FA |
|---|---|---|---|
| T. Brooks | Supervisor | All | |
| K. Ahmed | Biller | Lakeview, Bayside | |
| L. Ortiz | Accountant | All (finance) | off |
What it is
Admin, Supervisor, Biller and Accountant. Each sees what their job needs and nothing more. Accountants get finance and reports without the claims workbench; billers can be limited to their practices.
The problem it solves
When everyone is an admin, nobody is accountable. Real billing teams have clear lines between who builds, who approves and who reconciles.
Process
How it works, step by step
- 1
Invite your team
Add users to your company account.
- 2
Assign a role
Admin, Supervisor, Biller or Accountant.
- 3
Scope billers
Limit billers to the practices they handle.
- 4
Secure sign-in
JWT-based authentication with optional two-factor in settings.
What's included
Everything below is part of roles & permissions today.
- Admin: full ops plus the admin console
- Supervisor: full ops, limited user creation
- Biller: day-to-day claims and denials, practice-scoped
- Accountant: finance, reports and A/R only
- Optional two-factor authentication
- Role changes recorded in the audit log
The guardrail
Approvals and postings always carry the name of the person who made them.
Where it fits: tenancy model
The structure that lets one billing company serve many practices without ever mixing their data.
- MEDBIX
- 1
Billing company (tenant)
MEDBIXYour company account and staff.
- 2
Client practices
MEDBIXOne space per client.
- 3
Patients, encounters, claims, statements
MEDBIXBelong to a practice.
Audience
Who uses it
These roles work with this feature day to day. Access always follows what your admin assigns.
Works closely with
Deep dive
What Roles And Permissions means in daily ops.
Practical context for Roles And Permissions: how teams use it, where it sits in the loop, and what to ask in a demo.
- Tied to how billing work actually splits
- Clear on human vs machine responsibility
- Links into related MEDBIX areas
Practice
Where this shows up on a busy day.
From morning eligibility checks to end-of-day posting, Roles And Permissions connects to the queues your team already lives in.
- Morning coverage and claim build
- Midday scrub and approval
- Afternoon denials and patient pay
Control
Keep a person on the send button.
Whatever page you're on, MEDBIX keeps AI in a propose role. Approvals, posting and rule activation stay human.
- Named approvals
- Visible AI proposals
- Immutable audit trail
Next
See Roles And Permissions against your volume
Bring your payer mix and the friction you feel today. We'll map it onto sample data in thirty minutes.
- Sample data only
- Your questions drive the agenda
- Written follow-up after
Common questions
Can we create custom roles?
The four roles cover most teams. Tell us if your structure is different.
Is two-factor required?
It's available in settings; many companies make it policy.
Can doctors log in?
MEDBIX isn't a clinical tool, so there's no doctor clinical login. Providers are billing entities in the system.
Want to walk MEDBIX against your real claim mix?
Thirty minutes with sample data. We'll follow one claim through the gate, then talk about your payers, practices and where the rework hurts today.
Notes from the billing floor
Occasional, practical writing on denials, A/R and running a billing company. No spam, unsubscribe any time.