Many sub-accounts run several calendars to separate different types of work, for example Discovery Meetings, Site Measures and Quotes. At the moment, all appointments push to a single linked Google or Outlook calendar for each user. This means every booking lands in the same external calendar, regardless of which HighLevel calendar it came from.

This creates problems for teams. A site measurer only needs to see Site Measure appointments, but they either see everything or nothing. Staff end up sharing a cluttered calendar, filtering manually, or missing bookings. It also makes it harder to share one external calendar with a contractor or team member without exposing every other appointment type.

Proposed change

Allow each HighLevel calendar to be linked to a specific Google or Outlook calendar. For example, Site Measures would sync to a “Site Measures” Google calendar, and Discovery Meetings would sync to a separate “Sales” calendar.

Allow the sync direction to be set per calendar. Some calendars would use two-way sync, while others would be one-way (HighLevel to Google/Outlook only), so external events do not block availability on calendars where they are not relevant.

Keep the existing conflict calendar settings so availability checking still works across all linked calendars.

Benefits

Team members only see the appointments relevant to their role.

External calendars can be shared with staff or contractors safely, without exposing unrelated bookings.

Businesses with field work (trades, measures, installs) can run their schedules cleanly from their own calendar apps.

It reduces the need for workarounds such as Zapier automations or duplicate user accounts.

Who this affects

Any multi-calendar account, especially service businesses with separate sales, site visit and delivery teams.

Before you post it, it’s worth searching the board for “calendar sync per calendar” or “multiple linked calendars”. If a similar idea already exists, upvoting it and adding your use case as a comment usually gets more traction than starting a new request. If you’d like, I can also write a shorter version for the comment field.