Understanding Color Palettes in AddEvent 2.0

AddEvent 2.0 moves color palettes from per-calendar to account-level. That means one palette controls all calendars and events for your account, making colors consistent across your dashboard, public calendar pages, and embeddable views. This doc explains what changed, how migration works, and how to fix common issues.

What’s new in AddEvent 2.0 for Color Palettes

Account-level palettes: A single palette is applied to the entire account (all calendars).
Calendars & events: Colors from the account palette can be applied to both calendars and events.
Inherited event color: Events default to the same color as their parent calendar.
Automatic sync: Updating the account palette in Account Settings updates calendar palettes automatically.
Consistent dashboard: The account palette is used internally, so dashboard colors match public views.

Migration — What to Expect

If you created one custom palette in 1.0

Your custom palette will be available on the Account Settings page and is editable.

If you created multiple custom palettes in 1.0

Only the first custom color palette you created in 1.0 will be available as an account-level option in 2.0.
Custom palettes that were not applied to any calendars were removed during migration to reduce conflicts.

How Migration Affects Different Account Setups

Accounts with a single palette applied to all calendars

That palette (default or custom) becomes the account-level palette.
Public pages (landing/embeddable) — no change.
Dashboard — calendar colors will now pull from the account palette (previously, calendar colors always used the AddEvent default). Event colors will match public pages.

Accounts with multiple palettes across calendars

The account will be set to the AddEvent Default Palette during migration.
Public pages remain unchanged until you edit the account palette.
Dashboard may show a different color for events compared to public pages until you update the account palette — this can cause temporary mismatches.
You can select your first custom 1.0 palette in Account Settings and edit it to restore consistency.

Common issues & quick fixes

Events show incorrect colors

Open Account Settings → Color Palette.
Choose Use a Custom Palette.
Edit the palette as needed and reapply to events.

Dashboard colors don’t match public pages

Open Account Settings → Color Palette.
Select Use a Custom Palette.
Edit and reapply so the dashboard and public views match.

Events or calendars display black/white

Cause: an event or calendar is assigned a color that doesn’t exist in the current palette.
Fix: update the palette so each color “slot” has a valid color.

You previously used multiple tiny palettes (one color per palette)

Create a single custom palette containing all required colors.
Assign the preferred calendar color to each calendar.
In 2.0, events will inherit their calendar’s color so multiple one-color palettes aren’t needed.

You really want multiple custom palettes

AddEvent 2.0 no longer supports multiple palettes per account.
Benefits of the new system:
- Up to 20 custom colors per palette
- Consistent color display across all views
- Easier event & calendar management

FAQs

Q: Will my public calendar pages change after migration? A: No — public pages (landing and embeddable) will remain unchanged unless you edit the account color palette.

Q: My dashboard looks different after migration — why? A: Dashboard colors now reflect the account-level palette. If your calendars used different palettes previously, you may see a temporary mismatch until you set the account palette.

Q: Can you restore my old palettes if I need them? A: Palettes that were not applied to calendars may be removed during migration. If you need help recreating or restoring colors, contact support, and we’ll assist.

Q: How many colors can I have in a custom palette? A: Up to 20 colors.

Need help?

If you'd like us to bulk-update event colors, please contact support with your account details and request.