Provision prescribers and ops staff by role — individual logins, tenant-scoped permissions
Fizy Health team access is role-based provisioning inside your organization at app.fizy.health: organization owners invite prescribers, operations staff, and admins with individual credentials and permissions scoped to what each person should do. Prescribers attach NPI and DEA where applicable; staff may build carts and run ops without prescriber signing authority. Every patient-linked cart mutation writes to the audit trail under the acting user — shared passwords are not supported because they break HIPAA-aligned access controls and make rejection debugging impossible on refill day.
If you searched fizy health team, user roles, or staff access, this page explains who gets what inside the provider app after your organization is created.
Four steps to set up clinic team access.
Provision team access during onboarding — not after verification — so prescribers are ready when production ordering unlocks.
- 01
Owner creates the organization
The first signup user at app.fizy.health/signup becomes organization owner with full admin rights including invites and verification submission.
- 02
Invite prescribers with NPI
Add each ordering prescriber with their role. They attach NPI validated against NPPES and DEA where required for their protocols.
- 03
Invite operations staff
Provision ops users who build carts, manage patients, and run checkout without prescriber signing authority when your workflow separates those duties.
- 04
Review permissions before refill day
Confirm each user sees only the actions their role allows. Adjust access before high-volume ordering — not during it.
Role decisions to make before you invite the team.
Clear role boundaries prevent checkout failures and audit gaps when multiple people touch the same refill batch.
What you need first
- Prescriber roster with NPI List every provider who will appear on 503A orders. Each needs an individual login with NPI attached — not a shared clinic account.
- Ops staff who build carts Identify who adds patient lines and runs validation versus who holds prescriber authority. Role separation matches how your clinic already divides refill day.
- Admin who owns verification Assign one owner or admin responsible for verification document upload and team invite hygiene when staff turnover occurs.
How access works
- 01 Send invites during onboarding Do not wait for verification approval. Prescribers need time to attach credentials before your first production cart.
- 02 Verify NPI on each prescriber Confirm NPPES validation passes for every ordering provider before they appear on live order lines.
- 03 Deactivate departed staff promptly Remove access when team members leave. Stale credentials are a compliance risk on patient-linked ordering platforms.
Common access issues
-
Shared login for the front desk
Shared accounts break audit trails and role enforcement. Provision individual ops logins even for high-turnover front desk roles.
-
Prescriber cannot sign orders
Usually missing NPI attachment or wrong role assignment. Check user profile in organization settings and confirm prescriber role is active.
Platform capabilities teams use by role.
Different roles touch different surfaces — these outcomes are what prescribers and ops staff collaborate on after access is provisioned.
-
One formulary view across every 503A partner
Browse assigned compounders in a single catalog with search, favorites, and pass-through landed cost on each line.
-
Friday refills for every patient in one checkout
Build the whole refill day in one clinic cart and submit a single payment across new starts and refills.
-
Fewer paid orders rejected by the pharmacy
Validation catches SIG, licensure, and stock issues before you pay — not after rejection.
-
Quote patients with real per-vial cost before the consult
See resolved 503A landed cost in catalog and cart before checkout, with facilitation fee disclosed at payment.
What clinics ask about Fizy Health team access.
- Roles
What user roles does Fizy Health support?
Organizations provision owners, admins, prescribers, and operations staff with role-appropriate permissions. Prescribers attach NPI; staff may manage carts and patients without prescriber signing authority.
- Access
Can multiple staff share one login?
No. Each team member needs individual credentials for audit trails and role enforcement. Shared passwords break HIPAA-aligned access controls on patient-linked ordering.
- Prescribers
How do prescribers join my organization?
Organization owners and admins send email invites from app.fizy.health. Prescribers accept, set a password, and attach NPI validated against the NPPES registry.
- Admin
Who can invite new team members?
Organization owners and admins can invite users and assign roles. Limit admin access to people responsible for credential hygiene and verification document management.
- Security
Are team actions audited?
Yes. Patient-linked cart and order activity records the acting user in the audit trail. The Security page documents tenant isolation and compliance controls.
- Offboarding
How do I remove a departed staff member?
Deactivate or remove the user in organization settings at app.fizy.health. Do not share their credentials — revoke access and provision a new login for their replacement.
Provision your team before refill day.
Create your organization at app.fizy.health/signup, invite prescribers and ops staff with individual roles, and attach NPI before verification completes.