Setting up your brand kit

Edited

Overview

Your brand kit is the set of logos, colors, and fonts that flow into every public-facing surface in Chamberly: event pages, email templates, the storefront, and sponsor receipts. Set it up once and your whole experience looks like your chamber instead of generic SaaS.

Before you start

  • You need an org_manager role to edit the brand kit

  • Have your logo files ready (PNG or SVG, ideally with a transparent background)

  • Know your primary, secondary, and accent hex color codes

Step-by-step

  1. Open Settings > Brand Kit from the sidebar

  2. Upload your Primary logo (used on light backgrounds)

  3. Upload your Inverse logo (used on dark headers)

  4. Upload a Favicon (32x32 PNG works well)

  5. Set your Primary color, Secondary color, and Accent color using the hex pickers

  6. Choose a Heading font and Body font from the curated list

  7. Click Save — changes apply to new pages immediately and existing pages within a minute

Tips & best practices

  • Use a square primary logo so it looks right in email headers and the storefront nav

  • Pick an accent color with strong contrast against your primary — it gets used for buttons and links

  • Test your colors on a draft event page before announcing — what looks great in a swatch can clash on a real layout

  • Premier customers can override fonts per-event from Settings > Event Page Styling

FAQ

Will updating the brand kit break my live event pages?
No. Style changes flow into existing pages without breaking content or layout.

Can I use custom fonts?
Custom fonts (Google Fonts) are available on Pro and Premier tiers. Core uses the curated font list.

Do I need different logos for emails?
No. The same primary and inverse logos are used in emails. Make sure your inverse logo has a transparent background so it blends with dark email headers.

Related articles

  • Completing the 5-step onboarding wizard

  • Tour of the chamber dashboard

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.