All Policyholder Portal configuration happens in the Carrier Admin Console at client.briteapps.com. A super-user account gives you access to your carrier environment only — your console, your branding, your data. BriteCore staff can switch into your environment to assist, but only when explicitly invited through a support case.
What you need
- A Policyholder Portal super-user account. If you don't have one yet, your BriteCore Implementation Manager creates it during kickoff using the email address you provided.
- The temporary password sent to that email.
- Multi-factor authentication enabled on your work email account (recommended).
First-time sign-in
- Go to client.briteapps.com.
- Enter your work email address and the temporary password.
- You'll be prompted to set a new password. Use 12+ characters with a mix of letters, numbers, and symbols.
- Optional: turn on browser-level password autofill so you don't have to type it again.
Environments — Dev vs. Production
Every carrier gets two Policyholder Portal environments:
| Environment | URL pattern | What it connects to | Use it for |
|---|---|---|---|
| Development |
client.briteapps.com (dev workspace) |
Your BriteCore dev instance | Branding, copy edits, template testing, feature toggles, UAT |
| Production |
client.briteapps.com (prod workspace) |
Your BriteCore production instance | Live changes only — they affect real policyholders immediately |
Switch between environments using the workspace selector in the top-right corner. Always make and validate a change in Dev first, then replicate it in Production.
Tip: Bookmark each environment as a separate browser tab and label them clearly. Mistakenly editing production content is the most common avoidable error in the first 30 days.
What you'll see on the home screen
After sign-in, the admin console opens to Home, which surfaces:
- Global Charts — enrollment counts, daily active users, payments processed.
- Recent Builds — the most recent iOS and Android builds and their App Store / Play Store status.
- Quick links — Settings, Content, Templates, Appearance, Colors, Users.
Navigation map
The left sidebar is organized in two groups:
Configure (settings that change what insureds see)
- Settings — feature toggles and policy
- Content — all visible text strings
- Templates — email, SMS, push, header, footer
- Appearance — logos, favicons, hero images
- Colors — color tokens
Operate (day-to-day visibility and tools)
- Users — admin user management
- Builds — current iOS / Android build status, simulated mobile preview
- Charts — adoption and engagement metrics
- Communications — outbound message history
- Audit Log — who changed what, when
Inviting other admins
Only existing super-users can invite new admins.
- Open Users in the sidebar.
- Click Invite admin.
- Enter the person's name, work email, and role (Super Admin, Admin, or Read-only).
- Click Send invite. They'll get an email with a temporary password.
- Ask them to sign in within 7 days — invitations expire after that.
For more on roles and permissions, see Managing Admin Users.
Switching into a carrier environment (BriteCore staff only)
If you're a BriteCore Implementation Manager or Support engineer assisting a carrier:
- From your internal admin tools, open a support case linked to that carrier.
- Use the "Assist in carrier environment" action — this records the impersonation in the carrier's audit log.
- Make only the change requested in the case, then log out.
Carriers can see exactly which BriteCore user took which action and when, in their Audit Log.
Common sign-in problems
- "Account not found" — double-check the email; super-user accounts are case-insensitive but the address must exactly match what was provisioned.
- "Invalid credentials" — use the Forgot password link. A reset email arrives within 60 seconds; check spam.
-
Stuck on MFA screen — clear browser cookies for
client.briteapps.comand sign in again. If your MFA device is lost, contact BriteCore Support to reset.