The portal and apps render entirely under your brand. There's no BriteCore mark visible to insureds. Branding lives in two admin sections — Appearance (assets) and Colors (tokens) — and both push instantly to web, iOS, and Android.
Before you begin — assemble your brand kit
Collect these assets before opening the admin console. Vector files (SVG, AI, EPS) are best; raster files should be provided at 3x the intended display size to survive retina-quality rendering.
| Asset | Format | Size / notes |
|---|---|---|
| Primary logo | SVG (preferred) or PNG with transparent background | 600 × 200 px minimum at 1x |
| Square logo (app icon source) | SVG or PNG | 1024 × 1024 px, no transparency |
| Favicon | PNG or ICO | 512 × 512 px source |
| Splash / launch image | PNG | 2732 × 2732 px (covers iPad Pro through phones) |
| Hero / login background | JPG or PNG | 2880 × 1800 px, < 800 KB |
| Color tokens | Hex codes | Primary, secondary, background, text, success, warning, error |
If your brand guide already has these assets, ask your marketing team to share the latest versions before kickoff. Pulling the wrong shade of blue from a five-year-old PowerPoint is the single most common cause of late branding rework.
Configure Appearance
- In the admin console, open Appearance in the left sidebar.
- Upload Primary logo (used on portal header, sign-in screen, emails, and PDFs).
- Upload Square logo — this becomes the iOS and Android app icon.
- Upload Favicon — appears on browser tabs.
- Upload Splash image — shown for ~1 second on app launch.
- Upload Hero image — the background of the web sign-in page.
- Click Preview on Web, then Preview on Mobile (the simulated mobile preview is in Builds > Details) to validate every asset on every surface.
- Click Save.
Changes propagate to the dev portal in under 60 seconds. Mobile builds pick up new assets on the next build (see Mobile Apps for the build cadence).
Configure Colors
The portal uses a token-based color system. You set five tokens; the design system derives every other shade.
- Open Colors in the sidebar.
- Set the five core tokens by hex code:
- Primary — buttons, links, branded accents.
- Secondary — supporting accents, secondary buttons.
- Background — main page background.
- Text — primary text color.
- Semantic — success (green), warning (amber), error (red). Defaults are usually fine; override if your brand requires.
- Use the contrast checker at the bottom of the page to confirm text-on-background meets WCAG AA. Anything below 4.5:1 is flagged in red.
- Click Preview to see all controls (buttons, alerts, links) rendered in your palette.
- Click Save.
Accessibility: Every Policyholder Portal release is tested at WCAG AA. If your primary color produces poor contrast against white text, the contrast checker will block save. Adjust the hex value or pick a darker shade.
Branding rules of thumb
- One logo, three surfaces. Use the same primary logo across web header, app launch, and emails. Inconsistent logos confuse insureds who switch between web and app.
- Avoid white-on-white. A light secondary color disappears on the white background of bills and email templates.
- Test on a real phone. Simulator preview catches 90% of issues; the last 10% only show up on a 4-year-old Android device with a low-brightness screen.
- Lock the palette early. Iterate on copy and templates freely, but treat colors as a one-time decision per launch.
Updating branding after launch
Branding updates after launch are routine — a rebrand, a seasonal campaign, a new agent program. Just be aware:
- Web changes are instant once saved to production.
- Mobile changes require a new build, which is queued nightly. iOS App Store review takes 24–72 hours; Google Play takes 2–24 hours. Plan around launch dates.
- App icon changes are a major version bump under Apple's rules and trigger a fresh review cycle. Avoid more than one icon change per quarter.