Managing Named Insured and DBAs

Last updated: March 5, 2026

Overview

Accurate Named Insureds and DBAs (Doing Business As) ensure policies, applications, and certificates reflect the correct legal entity at the policy level. When you confirm these details upfront, you support clean form generation and reduce rework later in the process.

Note: A DBA does not have separate legal standing. In the event of a claim, the underlying legal entity is legally responsible.

Add a Named Insured or DBA

  1. Open the appropriate Policy record.

  2. In the Named Insureds component on the right side of the page, select New.

Untitled design (9).png
  1. When the edit screen appears, open the Type dropdown

  2. Select the appropriate type:

    1. DBA

    2. Other

    3. Other Named Insured

Untitled design (10).png
  1. Complete the required fields and any additional relevant information.

  2. Select Save.

  3. Alternatively, you can edit an existing Named Insured or DBA at any time by selecting the edit pencil icon next to the record.

Untitled design (11).png

View all insured and DBAs

  1. Open the appropriate Policy record.

  2. In the Named Insureds component on the right side of the page, click View All.

    Screenshot 2026-03-05 at 1.19.20 PM.png

Best practices

When adding a DBA:

  • Follow all carrier-specific guidelines.

  • Confirm naming requirements for policy issuance.

  • Verify certificate formatting expectations.

  • Ensure the underlying legal entity is clearly identified and associated with the DBA.

  • Review the policy setup before issuing forms or certificates.

Accurate setup at the start helps prevent downstream corrections and keeps documentation consistent across policies and certificates.

Troubleshooting

STRING_TOO_LONG error

If you see a STRING_TOO_LONG error when saving your Named Insured or DBA,  the value entered exceeds the allowed character limit for one or more fields. To resolve the issue, refer to 📄 Resolving STRING_TOO_LONG Errorfor step-by-step troubleshooting guidance.