Parent & Sub-Org Permission Templates
Standardizes team member permissions across a parent organization and its sub-organizations using reusable permission templates. Templates are built once at the parent level and applied to each sub-org as it's created, so every location starts with consistent, role-based access instead of one-off settings per user. Owners can layer sub-org-specific restrictions on top for sensitive actions like billing and patient data access.
Built by Core Engineering
The problem it solves
Organizations with a parent/sub-org structure need consistent, role-appropriate access to scheduling, billing, and patient data across every location, without configuring each team member's permissions by hand at every sub-org. Setting permissions individually per user doesn't scale across multiple sub-orgs and makes it easy for sensitive actions to end up available to the wrong people.
What's included
- Reusable member permission templates created at the parent-org level
- Template application to sub-orgs at time of creation
- Distinct templates for Owners/Admins versus other team member roles
- Sub-org-level permission overrides for scheduling, billing, and documentation
- Bulk permission updates via Healthie's API
How it works
An admin builds one or more permission templates at the parent organization level — typically a distinct template for Owners/Admins and separate templates for other roles — and assigns them to a sub-org when it's created. Permissions cascade down to the sub-org automatically at that point, but editing the template afterward does not retroactively update members who already have it applied. From there, sub-orgs can adjust permissions locally — restricting billing, patient data access, or branding control to specific roles — and bulk changes across many members at once can be made through Healthie's API.
Parent & Sub-Org Permission Templates standardize what team members can do across a multi-org hierarchy instead of setting permissions user by user. They're for organizations already running Sub-Organizations, where an admin builds templates once at the parent level — typically a separate template for Owners/Admins versus other roles — and applies them when each sub-org is created. Permissions cascade down at that creation point only; editing a template afterward doesn't retroactively change members who already have it applied. Sub-orgs can then layer their own restrictions on top for sensitive actions like billing and patient data access.
