Topics on this page

Services: BriteSuite environment setup guide

This guide walks the BriteCore Services team through setting up BriteSuite, which is built to be as configurable as possible straight out of the box.

Service request 

Owner: Project Manager

If you’re requesting a new client trial site, then:

  • Contact #cloud-int > Access Request Action:
    • Delivery Date
    • URL
    • Services 
    • Sizes

Django Admin access

Note: Django Admin access is integrated with BriteAuth.

Django is a Python-based, free, open-source web framework that follows the model–template–views architectural pattern. Django comes with a built-in admin interface. With Django’s admin features, you can automatically authenticate users, display and handle forms, and validate input. Django also provides a convenient interface to manage model data.

The web-based administrative backend tool allows trusted site administrators to create, edit, and publish content, manage site users, and perform other administrative tasks.

At BriteCore we use Django Admin to administer:

  • Quotes
  • Policies
  • Claims
  • Lines
  • Documents 

Users are authenticated by BriteAuth and Django sites are accessible at:

  1. Log in to the site: https://[subdomain]
  2. Navigate to the Django Admin url for each product: https://[subdomain][product]/django-admin/

Note: Django Admin isn’t currently used by Integrations and Rules.

Best practices when working with questionnaires

To ease the configuration of each product, we provide a questionnaire, linked in the respective sections below.

  1. Using the templates, familiarize yourself with each step of configuration and any templates available.
  2. Identify any information you can answer readily given client resources. 
  3. Make a copy of all templates and edit only the copies.
  4. Save the copies to a client folder in the appropriate Google Drive location.

Import from other sites 

Owner: Rating Business Configuration Analyst 

If you manage an existing site and want to replicate some of the configuration, you can use support tools to:

Enable advanced settings

Owner: Site Business Configuration Analyst 

Enable the following advanced settings:

Switch specific billing settings: 

Set business locations 

Owner: Site Business Configuration Analyst 

To build lines, you first need to set up business locations. Refer to the guide for working with business locations.

Add a primary carrier 

Owner: Site Business Configuration Analyst 

To add a primary carrier, you will Add a New Organization in the Contacts module and assign the organization the Primary Carrier role.

These steps brand the BriteCore site with the carrier’s name. It will also populate the carrier’s name on deliverables and reports. 

Attach an agency to a policy 

Owner: Site Business Configuration Analyst 

You must set the policy to Agency in BriteSuite. This allows other agents within the agency to access the policy information in case the assigned agent isn’t available. 

To set a policy to an agency:

Go to Advanced Settings > policy-go-to.

Set Policy numbering engine version to 1

Owner: Site Business Configuration Analyst 

The default policy numbering engine is Version 1. Adjust the setting to continue the numbering sequence from the previous year. To create custom policy numbering that supports state and policy type, follow the steps  below.

Create custom policy number (v2 numbering engine)

The BriteCore v2 numbering engine utilizes a  custom sequence framework. This package provides the ability to create composed sequence generators from textual descriptions.

Step 1: Enable numbering engine version 2

Figure 1: Advanced settings.
  1. Navigate to Settings > Advanced > Setting Sections > policies, or search for number-engine-version using the Search for a Setting box.
  2. Set the value of number-engine-version to v2.

Step 2: Configure v2 policy numbers

v2 policy numbers are configured in the database via format expressions.

Format expressions

Format expressions comprise sequence expressions, zero or more optional static characters, and zero or more additional options.

Example: P-{current_year}-{counter}

Sequence expressions

Sequences are expressed as ranges or sets of alphanumeric characters and defined within square brackets.

Examples: [1970-3000], [1-999999], [A-Z], [A,B,C], [1,2,3]

Sequences can be labeled using the < and > characters for referencing the sequence in format expressions.

Examples: <current_year>[1970-3000], <counter>[1-99999]

Note: If a sequence is not labeled it can be referenced in a format expression as follows.

  • {number} or {number0}: The first numeric sequence in the associated sequence expression.
  • {alpha} or {alpha0}: The first alphabetic sequence in the associated sequence expression.
  • {number1} and {alpha1}: The second numeric sequence and the second alphabetic sequence in the associated sequence expression, respectively.

Additional options

  2. Special fields
    1. {current_year_short} (last 2 digits of the year of the revision date)
    2. {term_number_per_year} (increment +1 per year since policy inception starting with 1)

Disable automatic nightly processing 

Owner: Site Business Configuration Analyst 

For the development and testing site, disable automatic nightly processing. 

Note: You can use Support Tools to manually set up your nightly processes.

Available options include:

  • Auto Pay Policies: Trigger automatic payment of policies setup for auto-pay.
  • Auto Renew Policies: Trigger automatic creation of renewal revisions.
  • Run Cancel & Non-Renew Processes: Handles canceling policies that the user has placed into Cancellation Pending, expires policies that were placed into Non-Renew, and generates the corresponding deliverables. This tool doesn’t handle Cancellation Pending for Non-Payment of Premium.
  • Run Non-Pay Processes: Handles placing a policy into Cancellation Pending for Non-Payment of Premium, evaluates whether the policy should cancel for Non-Payment of Premium and cancels when appropriate, and generates the corresponding deliverables.

Refer to Support Tools documentation for more details.

Generate API credentials via the UI

Owner: Technical Services

Refer to How do I get started?, a guide for developers. 

Assign access roles in BriteCore

Owner: Site Business Configuration Analyst 

The BriteCore administrator role is automatically created. To add more roles, refer to Assign roles to System Access Permissions

Configure BriteLines

Owner: Rating Business Configuration Analyst 

Refer to our BriteLines documentation for more details, including how to add a child product

Configure BriteQuotes

Owner: Site Business Configuration Analyst 

Refer to our Configure quotes screen flow documentation for more details. 

Adjust the quote flow so you can configure BriteQuote to bind

Add Agency Contact Lookups

You must associate your BriteQuote flow to the Agency. 

If your Quote Flow was auto-generated and add the following bold Type and Name of the component to the first page:


– name: setup


  – components:

    – type: associateContactsPanel

      name: associatedContacts

Figure 2: Sample code.

Refer to the Page Group documentation for more details. 

Add contact role type mapping 

Add contact mapping to map quote role types in BriteSuite: 

Navigate to the Quote Django Admin of the site at:

https://[name of site here]

Figure 3: Quote Django Admin.

Refer to this documentation for more details. The training video explanation starts at 2:45. 

Map named insured 


  • Role: Gen2:contacts
  • Risk type name: policy
  • Product name: <<Product Reference ID>>
  • Product version: <<leave blank>>

Field mappings

You have to add each of the following names and values as role references:

  • role: Named Insured
  • contact_type: individual
  • name: {{ firstNameNI }} {{ middleInitialNI }} {{ lastNameNI }}
  • address.address_line1: {{ streetAddressNI }}
  • address.address_city: {{ cityNI }}
  • address.address_state: {{ stateOfNI }}
  • address.address_zip: {{ zipCodeNI }}
  • address.address_countryz: USA

Map drivers 


  • Role: Gen2:contacts
  • Risk type name: drivers
  • Product name: <<Product Reference ID>>
  • Product version: <<leave blank>>

Field mappings

You have to add each of the following names and values as role references:

  • role: Named Insured
  • name: {{ driverName }}
  • address.address_line1: {{ driverAddress }}
  • address.address_city: {{ driverCity }}
  • address.address_state: {{ driverState }}
  • address.address_zip: {{ driverZip }}
  • address.address_country: {{ driverCountry }}

Create billing schedule risk type role mappings

Ensure that BriteQuote is integrated with classic Billing, set up billing schedules (refer to the Billing Schedule template for client options), and import billing schedules.

To create a billing schedule risk type role mapping:

Navigate to the Quote Django Admin of the site at:

https://[name of site here] and select Billing under Quotes. 

Figure 4: Change billing schedule screen.
  • Name:  <<Match with the name of the billing schedule in Policy Life Cycle Settings>>
  • External ID: <<id of the billing schedule>>

Copy the ids required above from the classic site: 

  • <client site>/britecore/settings/modulesPoliciesPolicyLifeCycle : You can open the Developer Console on your browser to view the Billing Schedule ids

Resource: Training Video: Billing schedule discussion starts at 21:25.

Create a BritePolicies screenflow

Refer to our Configure policies screen flow documentation.

Additional Resources:

Add classic police type 

Owner: Rating Business Configuration Analyst 

BritePolicies is also a hybrid of classic BriteCore and BriteSuite. We need to create a classic BriteCore shell of the policy type to connect the classic BriteCore and BriteSuite functionality. Child products associated with a state will insert a classic policy type. Imported or countrywide products must be mapped manually.

To map a classic policy type:

  1. Create a classic policy type with the same name as the BriteSuite policy type.
  2. Once created, update the database to match policy_types.britelinesProductName to match the Product Reference Name from BriteLines. 

Sample code

select id, name, britelinesProductName from policy_types where britelinesProductName <> '';

update policy_types set britelinesProductName = 'cautoCW' where id = '3349587d-2349-4b67-98c7-aa6f9df0454f';

If you don’t have access to the database, use the support tool: Copy Policy type.

Export using the support tools, update the britelines_product_name, name and sequence_id fields and re-import. 

Save Policy Type Life Cycles to initialize for this Product: <client-url>/britecore/settings/modulesPoliciesPolicyLifeCycle

Refer to the training video for more details. 

Configure Contacts permissions

Owner: Site Business Configuration Analyst 

To configure permissions for a contact using BriteQuote:

Configure Rules 

Owner: Rating Business Configuration Analyst 

Use the Rules template to outline client requirements. Each line of business has three Rules projects that are preconfigured for clients and administrators:

  • Quoting rules 
  • Form attachment rules
  • UI controls 

For Claims-specific rule sets:

  • Claims accounting
  • Claims notifications 

To learn more about Rules, refer to our BriteRules documentation.

To access the Rules Django Admin screen: <client url>/lines/django-admin/

Import Rules

Create a new project from the BriteRules Project Templates:

Configure BriteDocs

Owner: Technical Services

BriteDocs allows users to create and manage their own templates as well as generate documents in BriteCore.

To set up BriteDocs, you must complete three steps:

  1. Gather client requirements using the Deliverables triggers, Deliverables options, and the Deliverables recipient templates. In addition, gather the list of all deliverables the client will be using including mockups or samples of each document. 

Note: While the Configuration team can upload static PDF deliverables, any documents that require us to pull information from the lines built into the document will go to the developers.

  1. Refer to the BriteDocs configuration document for configuration steps as well as how to access the document generation dashboard to troubleshoot BriteDocs issues related to document and packet generation.

For additional resources, refer to this training video on how to set up documents and deliverables. 

Refer to our BriteDocs documentation for more information.

Configure BriteClaims

Owner: Technical Services/Products

You can configure BriteClaims via APIs. In addition, refer to the following resources: 

For more information on the BriteClaims module, refer to our BriteClaims documentation

Configure BriteSuite integrations 

Owner: Site Business Configuration Analyst 

Refer to our BriteSuite integration documentation to see what’s available. In addition, refer to the BriteSuite configuration page for information on how to configure the BriteSuite integrations.

Data Mapping 

Owner: Technical Services

You can use our APIs to map and transform your data.

Custom styles and themes

Owner: Project Manager

Submit a request for custom styles and themes to the Design team. 

Import users into BriteCore 

Owner: Technical Services

Import the users spreadsheet into BriteCore using specific formatting provided by BriteCore.  

Import Agent, Agency, and Agency group into the system

Owner: Technical Services

Import the agent, agency and agency group spreadsheet into BriteCore using specific formatting provided by BriteCore.

Set up contacts in BriteCore 

Owner: Site Business Configuration Analyst 

Use the Contact settings spreadsheet to track client requirements. Adjust the roles and related information of the imported users, agent, agency and agency groups in the Contacts module. The Contacts module and associated support tools and settings provide a robust contact management system. The Contacts module is accessible to administrators, employees, carriers, and underwriters.

Set up commission structures 

Owner: Site Business Configuration Analyst 

Use the commission structures spreadsheet to track client requirements. Refer to details on how to set up commission structures.

Configure user management permissions in BriteCore

Owner: Site Business Configuration Analyst 

General permissions settings can be configured under Settings within the System Wide Permissions section. The system-wide permissions control options for edit/delete privileges and create/edit permissions for groups of users (these define access by None, Read, or Read/Write).

Steps to set up permissions include: 

  • Review Role Level Permissions with [Client Name]: Discuss what access the client wants to enable for each role. Use the permission spreadsheet to document client requirements. 
  • Review System Wide Permissions: Discuss available options for permissions. The settings are granular per role. 
  • Set up Permission Levels: Set up the permission levels within Settings
  • Assign Permission Levels to Contacts: Add roles to users within the Contacts module. 

For more resources, review the post on how to assign permission level after a new user is created and this training video on permissions.

Configure authentication 

Owner: Cloud Team/Technical Services  

The Cloud team ships a site with BriteAuth already configured. However, if the client requires single sign-on (SSO), the Technical Services team will get involved. 

  • Document client federated identity requirements.
  • Enable MFA on the client site.
  • Enable BriteAuth on client BriteCore instance.
  • Configure BriteCore SSO.

Gather build information from the client

Owner: Project Manager/Business Analyst

Gather the following information from the client to continue building the site.

  • Identify subject matter expert (SME), or main point of contact for correspondence and testing.
  • Organize and finalize manuals.
  • Finalize rates (use an Excel file for the quickest implementation).
  • Finalize business rules.
  • Prepare a Rater with rating steps if not listed in manual; this is usually in an Excel document format to plug in values and confirm premium.
  • Provide list of 10–20 sample policies for premium comparison.
  • Provide PDFs of all forms.
  • Provide a sample declaration page.

Configure policy lifecycle settings

Owner: Site Business Configuration Analyst

Use the Policy lifecycle template to guide the client requirements. Policy Lifecycle  is configured within the Settings module under Policies. Select Edit Policy Lifecycle. 

Figure 5: Policy Lifecycle screen.

Refer to the Policy Lifecycle documentation and a training video as additional resources. 

Cancellation (Underwriting)

  • Review underwriting cancellation workflow with the client. 
  • Select options for system to follow.
  • Select documents to be used.
  • Configure earned premium.
  • Configure cancellation reasons.


  • Review non-renewal workflow with the client.
  • Configure non-renew reasons.
  • Configure notification for notice.


  • Review continuation workflow with the client.
  • Select Enable Continuation of Coverage (optional).


  • Review expiration workflow with the client.
  • Select Options.
  • Enter reinstatement prompt. This only applies to reinstating an actual expired policy past the normal notification period (late renewal), instead of rewriting the policy.

Note: If it’s a cancelled policy, you won’t see the prompt.

Configure billing and payments

Owner: Site Business Configuration Analyst 

Billing  is configured within the Settings module under Policies. Select Edit Policy Lifecycle. 


  • Configure options.
  • Set up billing schedules.
  • Set up write off reasons.
  • Review billing workflow with the client.


  • Set return premium amount.
  • Set up options for public payment and agency sweep.


  • Configure payments options.
  • Configure renewals options.
  • Configure length of non-pay.
  • Configure Fees for non-pay.
  • Set non-pay threshold.
  • Review non-pay workflow with the client.


  • Set up reinstatement fee.
  • Set up documents for reinstatement.
  • Set up reinstatement reasons; only applies to an expired policy.

Note: If you’re setting up a reinstatement mid term in a policy, you must fill it out manually.

  • Review reinstatement workflow (no lapse).

Build custom features (if applicable) 

Owner: Technical Services/Products in collaboration with Project Manager

If the client requests any custom features:

  • Define requirements.
  • BriteCore builds the feature.
  • Client accepts the feature.

Data conversion

Owner: Technical Services

Programmatically importing policy data into Britecore requires support from the Technical Services team. The other option would be to manually key in the data. 

Conduct client training

Owner: Business Analyst

Steps for client training include:

  • Discuss training options.
  • Prepare agent training materials.
  • Prepare underwriting training materials.
  • Prepare billing training materials.
  • Prepare claims training materials.
  • Conduct training.

Conduct user acceptance testing

Owner: Project Manager

Steps for user acceptance testing (UAT) include:

  • Define testing process.
  • Provide client with test plan.
  • Obtain sign-off for client acceptance.


Owner: Project Manager

To prepare for Go-Live, you need to:

  • Provide URL to BriteCore for site.
  • Have DevOps create site using provided URL and UAT site data.
  • Enter issue for DevOps to flip site live.
  • Confirm integration functionality.
  • Clear out policies test data from live site.
  • Clear out contacts test data from live site.
  • Clear out Claims test data from live site.
  • Clear out Claims Catastrophe test data from live site.
  • Confirm company logo and signature.
  • Confirm deliverables configured.
  • Confirm final forms uploaded to Lines.
  • Confirm ratings approved and locked down for Live.
  • Confirm policy lifecycle settings configured.
  • Confirm billing schedules and setup.
  • Confirm Claims > Perils is accurate.
  • Enter in email addresses for Administrative Alerts.
  • Create agency group, agency, and agent contacts.
  • Confirm commission rates.
  • Confirm Permissions: Agents, Agency, and Agency Groups set up for Day 1.
  • Confirm redirect/SSO works from client portal.
  • Confirm postfix settings.
  • Run pre-live queries.
  • Confirm Admin Dashboard is set up.
  • Confirm Agent Dashboard is set up.
  • Set up Zendesk.
  • Obtain Go-Live sign-off.
  • Convert test site to production site.