Home/HighLevel/Features/Calendars & Appointments/How to configure conflict checking in HighLevel calendars

Calendars and Booking

How to configure conflict checking in HighLevel calendars

In short

Conflict checking reads events from a user’s linked Google, Outlook, or iCloud calendars and blocks those slots in Round Robin, Service, Class, or Collective calendars. It stops new appointments from being scheduled when the user is already busy, without creating extra records.

AreaCalendars & Appointments · Calendar Settings & Preferences
Used forConsulting agency, Fitness studio, Online education platform
Setup steps5 steps in 1 task
Last updatedNovember 16, 2026

01Who this is for

  • Founders of service based firms that rely on round robin or collective calendars, to keep staff from being double booked.
  • Team managers who schedule classes or workshops across multiple experts and need to respect each member’s personal calendar.
  • Administrators of group calendars that sync with external calendars, to ensure all external commitments are considered.

02Calendar scheduling conflicts, explained

The feature reads every event from calendars linked to a user’s profile, Google, Outlook, or iCloud, and marks those periods as unavailable in HighLevel team calendars. When an external event exists, the platform prevents the creation of a new appointment that would overlap that time. No new appointment records are generated during this check.

Settings for this behavior are found under Settings > My Profile. Two options appear: Primary Calendar, which designates the main external calendar for syncing, and Check for Conflicts, which determines which linked calendars are consulted to block busy times. All external calendars that the user has previously added are listed in these sections.

If a calendar is turned off in the Conflict section, it is assumed to already serve as the Primary Calendar. This ensures that the same calendar is not evaluated twice. The conflict logic works only for team or group calendar types such as Round Robin, Service, Class, and Collective calendars.

03How businesses use calendar scheduling conflicts

  • Consulting agency. The agency links each consultant’s Google calendar, then enables conflict checking. When a client tries to book a strategy session, the system automatically blocks times that the consultant already has meetings, avoiding double bookings.
  • Fitness studio. The studio sets up a class calendar and connects each trainer’s Outlook calendar. By turning on conflict checking, any personal appointments in the trainers’ Outlook calendars prevent class slots from being offered at those times.
  • Online education platform. Course coordinators add iCloud calendars for guest instructors. Activating conflict checking ensures that live webinar slots are hidden when an instructor is flagged as busy in their personal calendar.

04The numbers and rules that matter

  • Supported third party calendars: Google, Outlook, iCloud.

05Before you start

  • User must have at least one external calendar (Google, Outlook, or iCloud) integrated under Settings > My Profile.
  • The calendar must be part of a team or group calendar type such as Round Robin, Service, Class, or Collective.

06How to set up and use calendar scheduling conflicts in HighLevel

Configure calendar conflict checking

  1. Open Settings and select My Profile.
  2. Locate the Primary Calendar option and verify the desired external calendar is selected.
  3. Find the Check for Conflicts setting below the primary option.
  4. Review the list of linked Google, Outlook, or iCloud calendars displayed.
  5. Toggle each calendar on or off to control whether its events block appointment times.

07What it looks like in HighLevel

08Settings that matter

  • Primary Calendar. Specifies which external calendar serves as the main source for syncing events into the HighLevel system.
  • Check for Conflicts. Determines which linked external calendars are consulted to block times when the user is unavailable.

09Things to know before you rely on it

  • Disabling a calendar in the Conflict section means it is already set as the Primary Calendar.
  • The conflict feature only reads events; it does not create appointment records.

10How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Calendar scheduling conflicts are a solid way to keep your team’s booking windows clean.

If you don’t rely on external calendars to manage availability, you can skip this feature.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 16, 2026

Common questions

Common questions about calendar scheduling conflicts.

What calendars are considered when conflict checking is enabled?

All Google, Outlook, and iCloud calendars that the user has integrated under Settings > My Profile are read for busy times.

Does enabling conflict checking create extra appointments in HighLevel?

No. The feature only reads external events and blocks overlapping slots; it does not generate new appointment records.

Can a calendar be both primary and selected for conflict checking?

If a calendar is turned off in the Conflict section, it is assumed to already be the Primary Calendar, preventing duplicate evaluation.

Where can I find the settings to enable or disable conflict checking?

Navigate to Settings > My Profile; the options appear under Primary Calendar and Check for Conflicts.

Is conflict checking available for individual calendars?

The feature applies to team or group calendar types such as Round Robin, Service, Class, and Collective calendars.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.