Scripts multi-location access
Scripts multi-location access is how a clinic group or telehealth brand orders and manages users across more than one site on the platform. Scripts markets 'one login, one invoice' across its pharmacy network — designed for telehealth brands scaling nationwide — but it does not publish the details of its organization hierarchy, whether one login spans multiple distinct clinic entities, or how locations are separated. Multi-site operators and telehealth brands should confirm how locations, users, and ordering are structured before standardizing on Scripts across a group.
This page frames the multi-location questions to ask Scripts and how Fizy Health structures one login across organizations and clinic locations.
Proudly Partnered With
Confirm how sites, users, and orders separate.
Scripts positions itself as a fulfillment backbone for telehealth brands scaling nationwide, with one login and one invoice across its pharmacy network. For a single clinic the model barely matters. Across a group, it decides whether your team can switch sites from one account or must juggle separate setups, and whether ordering and patient records stay cleanly separated per location.
What you need first
- A clear organization-to-location mapConfirm how Scripts represents a parent telehealth brand and its clinic sites so orders and users attribute to the right location.
- A defined user-access model per siteConfirm whether a user can be scoped to one location or many, and how an admin manages access across the group under the one-login model.
- Separation of ordering and patient recordsConfirm that patients, orders, and history stay separated per location so sites do not see each other's data, even under one login.
How access works
- 01Ask how locations are structuredHave Scripts explain whether multiple clinic sites live under one organization and how that hierarchy is represented in the portal and on invoicing.
- 02Confirm the login and invoice modelDetermine whether 'one login, one invoice' means a single clinic or scales to multiple sites under one account.
- 03Scope users per locationMap which staff and prescribers need which sites, and confirm an admin can grant and revoke access per location.
Common access issues
Separate vetting calls per site
If each location needs its own Apply and Verify vetting call, multi-site standardization takes longer. Confirm whether a group can onboard under one process.
Blurred data between sites
Without clear separation, one location can see another's patients or orders. Confirm isolation across the group even under a shared invoice.
Evaluating Scripts for multiple sites — or comparing multi-clinic access?
Scripts
Your group's structure matches what Scripts confirms it supports.
- You will confirm directly how Scripts represents organizations and locations before standardizing.
- Email support at support@scripts.co handles your multi-site access questions.
- Your telehealth brand scales with concierge fulfillment and one consolidated invoice.
Fizy Health
You want one login across every clinic and organization.
- You want a single account with org and clinic switchers for every location you manage.
- You want users scoped by role per clinic with clean separation of patients and orders.
- You want staff covering multiple sites to switch locations without signing in and out.
What true multi-clinic access unlocks.
Across a group, the access model is the workflow. These outcomes follow from one login built for multiple locations.
One login for every clinic you run
Switch between organizations and clinic locations from a single account instead of separate setups per site.
Scope users by role per location
Grant prescribers and staff access to the exact sites they cover, with NPI and DEA validated by role.
One catalog across all sites
Every location browses the unified 503A formulary with consistent pass-through pricing.
Batch each site's refill day in one cart
Build a location's whole refill day into one clinic cart for a single validated checkout.
What multi-site clinics ask about Scripts access.
- Definition
What is Scripts multi-location access?
Scripts multi-location access is how a clinic group or telehealth brand orders and manages users across more than one site on the platform, including how one-login and one-invoice work across multiple clinic entities.
- Login
Does Scripts use one login across locations?
Scripts markets 'one login, one invoice' and is positioned for telehealth brands scaling nationwide. Whether that extends to multiple distinct clinic entities or requires separate onboarding per site is not detailed publicly — confirm with Scripts before standardizing.
- Structure
How does Scripts represent a clinic group?
The public site does not detail an organization hierarchy for multi-site groups. Ask Scripts how a parent telehealth brand and its sites are structured so orders, users, and invoicing attribute to the correct location.
- Data
Are patients and orders separated between Scripts locations?
Confirm with Scripts that patients, orders, and history stay isolated per location so one site cannot see another's data — clean separation matters even when operating under a single login and consolidated invoice.
- Onboarding
Does each Scripts location need its own vetting call?
Scripts does not publish whether multi-site groups onboard under one Apply and Verify process or whether each location needs a separate vetting call. Confirm the group onboarding path before you plan a multi-site rollout timeline.
- Alternative
How does Fizy Health handle multiple locations?
Fizy Health gives one login with org and clinic switchers for every location you manage, scopes users by role per clinic, keeps patients and orders cleanly separated across sites, and is free to start.
Sources reviewed June 2026
- Scripts public website (scripts.co), reviewed June 2026.
- HRT University podcast ep. 67, reviewed June 2026.
- Fizy Health platform capabilities reflect the live product.
Run every clinic from one login.
Fizy Health gives multi-site groups org and clinic switchers, role-based access per location, and clean data separation. Free to start.