Skip to main content

GHL Calendar Primary Color SOP

1. Purpose & Scope​

Set the Primary color on a GHL calendar's Neo widget so that embedded calendars and public booking links render in the client's brand color instead of the default GHL blue (#178af6).

Every Symphony Core client has at least one calendar modified during onboarding, so this SOP is a standing task per client.

In scope:

  • The Primary color field inside Widget appearance → Primary settings for one calendar at a time.

Out of scope (each would warrant its own SOP if frequency justifies):

  • Background color, Button Text, Calendar title / description toggles, cover image.
  • Switching between Neo and Classic widget styles.
  • Availability hours, buffers, meeting types, staff selection — see the Client Onboarding Verification CALENDARS section.

Trigger:

  • New client onboarding (first calendar branding).
  • Client rebrand or design-kit update.
  • A new calendar is added to an existing client.

2. Prerequisites​

  • Agency or sub-account access to Settings → Calendars for the target client.
  • Client location ID and the target calendar identified.
  • Client design kit exists. The color_primary hex lives in:
    • 09-clients/<slug>/<slug>-client-profile.md → section ## Brand Design System → Colors table (source of truth), or
    • Client_Delivery/<slug>/client-reference/design-kit.pdf (published client-facing copy).
  • Calendar widget style is already set to Neo. Widget appearance customization only applies to Neo. If the calendar is on Classic, flag to the account lead before proceeding — switching styles is out of scope.

3. Steps​

  1. In the target sub-account, open Settings → Calendars.
  2. Find the target calendar in the list and click the edit (pencil) icon.
  3. In the left nav of the calendar editor, expand Advanced settings and click Widget appearance.
  4. Under Calendar widget style, confirm Neo is selected.
  5. Under Primary settings → Primary color, replace the existing value with the client's color_primary hex. Use #RRGGBB format (6 hex digits with leading #). GHL also accepts #RRGGBBAA; only use the 8-digit form if the design kit explicitly specifies alpha.
  6. Click Save changes (top right).
  7. Verify: open the calendar's public booking link in an incognito window and confirm the CTA button and selected-date chip render in the new color. GHL caches widgets aggressively — use incognito or hard-refresh.
  8. If the client has more than one calendar, repeat for each. Record completion in the client's onboarding tracker or ClickUp checklist.

4. Quality Check​

  • Hex value matches the design kit exactly — no typo, no legacy color.
  • Public booking link shows the new color on the primary CTA button and the selected-date highlight.
  • All active calendars for the client have been updated.

5. Troubleshooting​

"Only works with Neo widget" banner still showing. Neo is not actually selected; re-toggle between Classic and Neo, then save.

Color saved but public link still renders the old color. GHL caches public calendar widgets. Hard-refresh the page or reload in an incognito window. Allow up to a few minutes for edge caches.

Hex value rejected by the input. Ensure the value starts with # and has exactly 6 or 8 hex characters. No spaces, no named colors.

Design kit says TBD for primary color. Stop — do not invent a value. The color kit must be populated first by the engagement lead per the design kit pattern in the client profile.

6. Reference​

  • Source of truth (per-client hex): 09-clients/<slug>/<slug>-client-profile.md → ## Brand Design System → Colors.
  • Client-facing copy: Client_Delivery/<slug>/client-reference/design-kit.pdf.
  • GHL UI path: Sub-account → Settings → Calendars → [calendar] → Advanced settings → Widget appearance.
  • Related:

Document Owner: Symphony Core Operations Team Review Schedule: Annually, or whenever GHL changes the Widget appearance UI.