Calendar Sync for Sub-Organizations
Sync an external Google Calendar into multiple sub-organizations separately, with each synced calendar clearly labeled so availability doesn't get confused across sub-orgs. Useful for a team member operating across more than one sub-organization, such as someone licensed in multiple states under separate sub-org structures. Availability set at the Parent Org level trickles down to any sub-org that user belongs to, so each sync needs individual configuration.
Built by Core Engineering
The problem it solves
A team member working across multiple sub-organizations needs their external calendar availability reflected accurately in each one, but syncing the same external calendar into multiple sub-orgs without clear labeling risks confusing which availability belongs to which sub-org. This solves that by giving a clear process for syncing and distinguishing calendars per sub-org.
What's included
- Per-sub-organization Google Calendar sync configuration
- Calendar renaming convention for distinguishing sub-org calendars
- Checkbox selection of which synced calendar applies to which sub-org
- Parent Org availability trickle-down to member sub-orgs
- Manual Google-side sharing required for team members to view a synced sub-calendar directly
How it works
A user syncs their calendar from within the first sub-organization, then renames that calendar in Google to clearly indicate which sub-org it corresponds to, such as including a state abbreviation and initials. They repeat the same sync and renaming process from within the second sub-organization. From Settings > Calendar Sync in each sub-org, the user checks off which pulled-in calendar should apply to that specific sub-org's availability. If other team members need to view a synced sub-calendar in Google Calendar directly, that sub-calendar needs to be explicitly shared with them, since Healthie syncing alone doesn't grant Google-side visibility.
Calendar Sync for Sub-Organizations lets a team member who works across more than one sub-organization sync their external Google Calendar into each sub-org separately, while keeping the source calendars distinguishable. It's built for providers or admins operating in multiple sub-orgs (for example, licensed in more than one state under separate sub-org structures) who need their availability from each sub-org reflected accurately without the calendars getting confused with one another. Since availability set at the Parent Org level trickles down to any sub-org that user is a member of, each sub-org's calendar sync needs to be configured and clearly labeled individually.