The Settings page in the admin console controls how the portal behaves — what features are on, how authentication works, when notifications fire, and which product lines see which capabilities.
Most carriers ship with the defaults BriteCore configures during kickoff and only revisit Settings when their book or product mix changes.
Where to find it
Open Settings in the left sidebar of client.briteapps.com.
Settings is organized into seven sections, each editable independently:
- Authentication
- Enrollment
- Features
- Payments
- Claims
- Notifications
- Languages
1. Authentication
| Setting | What it controls | Default |
|---|---|---|
| Password minimum length | Required password length for insureds | 10 characters |
| Password complexity | Require letter + number + symbol | On |
| Lockout threshold | Failed attempts before account locks | 5 |
| Lockout duration | How long the account stays locked | 15 minutes |
| MFA required | Force MFA for all insureds | Off |
| Verification code TTL | How long the email verification code is valid | 10 minutes |
| Session timeout | Minutes of inactivity before sign-out | 30 |
Tip: MFA-required is rarely used for personal lines (it hurts adoption) but is common for commercial lines and group policies.
2. Enrollment
Controls whether and how insureds can enroll themselves.
| Setting | Effect |
|---|---|
| Self-enrollment enabled | Off = no public enrollment page (closed-book carriers); On = standard |
| Enrollment identifiers | Policy number + ZIP (default), or policy number + DOB |
| Verification channel | Email (default) or SMS — affects which verification template fires |
| Auto-link related policies | Multiple policies under the same billing account auto-link after first enrollment |
If self-enrollment is off, insureds can only access the portal after a CSR provisions an account for them.
3. Features
Per-feature on/off, applied per product line (you can enable autopay for personal auto but not for commercial).
| Feature | What it shows |
|---|---|
| Documents | The Documents tab — declarations, endorsements, ID cards |
| Pay one-time | One-time payment flow |
| Autopay | Recurring payment setup |
| Partial payments | Allow paying less than the full balance |
| Claims FNOL | Submit a claim from the dashboard |
| Claim photo upload | Attach photos to a claim (requires Claims FNOL on) |
| Claim video upload | Attach video (off by default; on for some storm-prone lines) |
| Agent contact card | One-tap call/email/text to assigned agent |
| Paperless billing toggle | Insured can opt into paperless from Profile |
| Renewal countdown card | Dashboard widget showing days until renewal |
4. Payments
| Setting | Notes |
|---|---|
| Processor | Read-only — set during implementation; matches your existing BriteCore processor |
| Accepted methods | ACH, Visa, Mastercard, Amex, Discover (toggle each) |
| Fee handling | Pass-through (insured pays fee), Absorb (carrier pays), Split (carrier pays X%, insured pays rest) |
| Minimum payment | Floor for one-time payments — defaults to $1 |
| Autopay draft date | Days before due date the autopay charge runs (default 5) |
| Receipt format | Email + PDF attachment, Email only, or Disabled |
5. Claims
| Setting | Notes |
|---|---|
| Loss types | Six tiles by default — auto edit per product line |
| Photo file size cap | Default 20 MB per file |
| Photo file count cap | Default 20 files per claim |
| Required fields | Date of loss, location, description (always); add custom fields per product |
| Adjuster auto-assign | Round-robin (default), product-line routing, or carrier-defined rule |
| FNOL deadline enforcement | Enforce a 24h or 48h cutoff if your claims rules require |
6. Notifications
Set the default channel mix per event type. Insureds can override per-event in their Profile (unless you mark it required).
| Event | Default channels | Insured can disable? |
|---|---|---|
| Bill due reminder | Email + push | Yes |
| Payment confirmation | No (regulatory) | |
| Payment failure | Email + SMS | No |
| Claim received | Email + push | Yes |
| Claim status update | Push (email fallback) | Yes |
| Policy renewal notice | No (regulatory) | |
| Cancellation notice | Email + SMS | No (regulatory) |
7. Languages
Toggle each language you want to support. The default pair is English and Spanish. Adding a language exposes a per-language tab in Content and Templates (see Content & Templates).
Saving and rolling out changes
- Every Settings save is logged to the Audit Log with the editor's user, timestamp, and before/after values.
- Setting changes apply immediately to the dev portal.
- Promote to production via the Promote button at the top of the Settings page (or wait for the nightly auto-promotion if enabled).
- Some changes (e.g., enabling a new language, changing the processor) require a brief blackout window — BriteCore will coordinate.
Common tuning patterns
- Adoption is slow in month 1? Lower the password minimum length to 8 and disable MFA required if it's on.
- Too many CSR calls about codes expiring? Increase Verification code TTL from 10 to 30 minutes.
- Autopay enrollments low? Check Bill due reminder copy in Templates — the call-to-action is the lever, not the toggle.