For clinic groups
One operating view across authorized clinics.
For dental groups that need authorized clinic access, group-level signals, and a shared operating view. Each location can start through a guided standalone pilot or keep an approved connection while staff move between permitted clinics and each request remains scoped to an active clinic.
Running one independently managed clinic? See the one-clinic path →
Built for the people consolidating across clinics
Practice managers, owners, operations leads, and authorized group staff can review how clinic access, switching, rollups, and workflow scope should work across their locations. Start mode, record ownership, enabled modules, import work, and rollout sequence are agreed clinic by clinic before a pilot starts.
What multi-clinic ops actually need · 1
Clinic-scoped access, enforced in the data layer.
Oralstack uses PostgreSQL row-level security to enforce tenant scope and only surfaces clinics an organization user is authorized to reach. Organization staff and access management support onboarding, offboarding, and clinic switching without treating every location as an unrelated login.
What multi-clinic ops actually need · 2
One organization view without flattening clinic boundaries.
Authorized staff can switch between permitted clinics and review group health or today-KPI rollups, then return to clinic-level work. Organization membership, active-clinic binding, and row-level tenant controls keep each request inside its allowed scope.
What multi-clinic ops actually need · 3
Operations analytics that surface where operators look.
Authorized managers can review group health and today-KPI rollups, then move into clinic-level booked and collected trends, outstanding payer amounts, daily-close work, and today-only provider and chair utilisation. Estimated or inferred measures stay labeled as such.
What it costs
$200 × clinics
Pilot pricing applies per clinic. Core setup is included; legacy-record work, optional connections, rollout sequence, controlled modules, and any group pricing are recorded in the proposal and MSA.
Talk to us about a group pilot. Full pricing →
Questions multi-location operators ask first
- Tenant isolation: Postgres row-level security and request-scoped clinic binding enforce tenant scope; the workspace only surfaces clinics the organization user is authorized to reach. Security posture →
- Audit evidence: audited actions are linked with an HMAC chain so integrity checks can detect alteration. Deployment-specific evidence is confirmed during procurement. Security and audit posture →
- Rollout: clinic start mode, access scope, enabled modules, and optional connections are planned location by location. We do not present a fixed full-record migration timeline as a product feature. Current product scope →
- Reporting: booked and collected trends, outstanding payer amounts, daily-close views, provider performance, today-only utilisation, and CSV where exposed. Operations workflow →
Scope a clinic-group pilot.
Tell us how your locations are organized, how each clinic should start, and which workflow should improve first. Record ownership, clinic sequence, access scope, optional connections, and enabled modules are agreed in writing for the pilot.