Skip to main content

Agencies

Written by Sven Gerlach

Overview

The Agencies page is where you keep a single inventory of your top company and every branch underneath it, see which Designated Responsible Licensed Persons are covering each one, and pull fresh license and appointment data from NIPR for one agency at a time or for many at once.

What is the Agencies Page?

The Agencies page is the operational roster for your organization in Turris. It gives you a single screen to verify that every branch has been onboarded, that the right DRLPs are attached to each one, and that NIPR compliance data has been retrieved recently enough to trust.

Who uses it. Compliance managers and licensing operations leads at the agency. They open this page when onboarding a new branch, when an audit asks for proof of DRLP coverage, or before kicking off a state-by-state license review that depends on current NIPR data.

Key capabilities:

  • See every top company and branch in your organization in one table, with the NPN and EIN already in view so you don't have to drill in to identify them.

  • Confirm at a glance which Designated Responsible Licensed Persons are assigned to each agency, and jump straight to any DRLP's agent record.

  • Spot agencies that have never had compliance data retrieved (or whose retrieval failed) and start a sync directly from the row.

  • Run a single bulk sync across many selected agencies after onboarding, so every branch is up to date in one operation.

  • Assign new DRLPs or fill in missing date-of-birth and Social Security Number data on existing DRLPs without leaving the page.

  • Open any row to drill into the per-agency detail dashboard for the full license map, alternate legal names, and PDB report.

Accessing the Agencies Page

Open the page from Left sidebar → Agencies. The page loads with every agency in your organization listed, and any filter or search you applied last time is preserved in the URL.

Note: If your organization uses customized terminology (for example, claims organizations referring to their entities as "Claims Orgs"), the left-sidebar label and the page title will reflect that wording. The filters and columns described below behave identically regardless of label.

What's visible on the page:

Column

Description

Selection

A checkbox at the start of each row, plus a master checkbox in the header. Visible only when you have permission to sync compliance data. Selecting one or more rows enables the Actions dropdown above the table.

Agency

A circular avatar with the agency's initials next to the agency's legal name. The branch name (if any) appears in smaller muted text directly beneath the legal name.

ID

The agency's EIN (Employer Identification Number) and NPN (National Producer Number). Either may be blank if not on file.

Type

A badge labeled Top Company for the organization's parent entity or Branch for every other entity that sits beneath it.

DRLP Agents

Up to three Designated Responsible Licensed Persons displayed as clickable badges. If more than three are assigned, a +N badge appears at the end — click it to reveal the rest in a popover. Each agent badge links to that agent's detail page. A dash (—) is shown when no DRLPs are assigned.

Data synchronization status

A colored badge showing the current state of NIPR data retrieval (see §Data Synchronization Status Reference). When the badge reads Not Started and the agency has an NPN, a small green cloud-download icon appears next to it — click it to start the sync.

Actions

A three-dot icon at the end of the row. Visible only to users with permission to assign or update DRLPs. Opens a popover with Assign DRLP and/or Update DRLP entries.

Click anywhere on a row (except a DRLP badge, the sync icon, or the actions menu) to open that agency's detail page.

If your organization structure has not been set up yet, the table is replaced by an empty-state card reading No data available — No agencies found. Please set up your organization structure first.

Synchronizing Compliance Data for a Single Agency

When you'd do this. A newly added branch shows Not Started, or you've just been told that an existing agency picked up a new license outside Turris and you want the dashboard to reflect that. Sync pulls the latest license and appointment data for the agency from NIPR.

  1. Locate the agency in the table whose Data synchronization status badge reads Not Started.

  2. Click the green cloud-download icon shown directly to the right of the badge. Hovering it shows the tooltip Start Data Synchronisation.

  3. The Data Synchronisation confirmation dialog opens. Read the description — it confirms that the operation will retrieve all of the agency's license and appointment data and may take a minute to complete.

  4. Click Start Synchronization.

  5. The badge transitions to Queued while the job is waiting for a worker, then Processing while NIPR data is being retrieved and ingested, and finally Success (green) when complete. If the retrieval or processing step fails, the badge reads Error (red).

Note: The inline sync icon only appears when the row's status is Not Started AND the agency has an NPN on file. Agencies without an NPN cannot be synced from this page — they show Not Started without the green icon. To start a fresh sync on an agency that previously succeeded or errored, open the agency's detail page from the row.

Synchronizing Compliance Data in Bulk

When you'd do this. You've just onboarded a multi-branch organization and need to pull NIPR data for every branch in one operation, or you want to refresh the compliance data for a subset of branches that share a renewal cycle.

  1. Use the checkboxes in the first column to select one or more agencies. The header checkbox toggles all currently visible rows. The Actions dropdown remains disabled until at least one row is selected.

  2. Click the Actions button at the top right of the page.

  3. Click Sync Compliance Data in the dropdown. The button's hover text confirms exactly how many agencies will be synced (for example, Start synchronization for 6 agencies).

  4. The Bulk Data Synchronisation confirmation dialog opens. It explains that license and appointment data will be retrieved for every selected agency and that the process may take a few minutes.

  5. Click Start Synchronization.

  6. A success toast confirms that compliance data retrieval started for the selected agencies, and each row's badge updates independently as its sync moves from Queued through Processing to Success (or Error).

Tip: Bulk sync is the fastest way to bring a newly onboarded organization up to date. Select every branch on the first day, then leave the dashboard open — each row updates in place as its data arrives. You don't have to wait for one row to finish before another can start.

Assigning a DRLP

When you'd do this. A new branch has been added and you need to designate which licensed agents are accountable for compliance in each state, or an existing agency is expanding into new states and needs DRLP coverage extended.

  1. Find the agency in the table and click the three-dot icon at the end of the row.

  2. Click Assign DRLP in the popover.

  3. The Assign DRLPs slide-over opens, subtitled Select one or more agents to designate as Designated Responsible Licensed Producers. A table lists every agent already associated with the agency, with a state multi-select control on each row.

  4. For each agent you want to designate as a DRLP, pick the states they should cover. Agents who already have DRLP states assigned arrive with those states pre-selected.

  5. Click Submit.

  6. The slide-over closes and the DRLP Agents column on that row refreshes with the updated badges.

Note: The slide-over only lists agents already associated with this agency. If the table is empty, you'll see No Agents Found with a link reading Go to Agents page to add agents →. Add the agent first, then return and assign them here.

Updating Missing DRLP Data

When you'd do this. A DRLP is on file but their date of birth or Social Security Number is missing, blocking license actions that rely on those personal identifiers (for example, NIPR-based filings that need the identifiers to match the producer record).

  1. Find the agency in the table and click the three-dot icon at the end of the row.

  2. Click Update DRLP in the popover.

  3. The Update Missing DRLP Data slide-over opens, subtitled Add date of birth and SSN for compliance tracking. Each DRLP on the agency appears as its own collapsible section, titled with the agent's name; the first section is expanded by default.

  4. Expand a DRLP and fill in whichever fields are missing:

Field

Required

Description

Date of Birth

Optional

The agent's date of birth, used for compliance tracking. Pre-filled if already on file; future dates are not selectable.

Social Security Number

Optional

Entered in 123-45-6789 format and masked as you type. Stored securely and used for NIPR identity verification. A small indicator shows whether an SSN is already on file.

  1. Click Save All at the bottom of the slide-over.

  2. The slide-over closes and the DRLP records on this agency are updated.

Note: If you click Save All without changing anything, you'll see a No changes detected message asking you to fill in the missing data for at least one DRLP. If the agency has no DRLPs assigned yet, the slide-over instead reads No active DRLPs found — Please assign DRLPs for this agency first. Use the Assign DRLP flow above before returning to update missing data.

Filtering and Searching

Two badge-style filter groups sit above the table.

Filter

Type

Purpose

Example use

Type

Badge toggle (Top Company, Branch)

Limit the table to top-company entities, branches, or — when no badge is selected — both.

Auditing only branches? Click Branch to hide the top company while you work.

Sync Status

Badge toggle (Success, Processing, Not Started, Error)

Filter to agencies in a single sync state. Processing covers both Queued and Processing rows. Error covers NIPR-side errors and ingestion errors.

Investigating sync failures? Click Error to surface every agency that needs intervention.

The table's built-in search box matches against legal name and branch name (fuzzy — typing "Indem" finds "Northern Indemnity"), and against NPN and EIN (substring — typing "8421" finds an NPN containing those digits in order). Search and filters compose, so you can narrow by Branch + Not Started and then type part of an NPN to land on a specific row.

Data Synchronization Status Reference

Color

Label

Meaning

What to do about it

Neutral

Not Started

No NIPR sync has been initiated for this agency yet.

If the agency has an NPN, click the inline green cloud-download icon to start a sync, or include the row in a bulk sync via Actions → Sync Compliance Data. If there's no NPN, add one through the agency's detail page first.

Primary

Queued

A sync has been requested and is waiting for a worker to pick it up.

Nothing — the row will move to Processing automatically within seconds.

Yellow

Processing

The sync is actively running. NIPR data is being retrieved and ingested.

Nothing — wait for the badge to settle on Success or Error. Most syncs complete in under a minute.

Green

Success

The most recent sync completed and the agency's licenses, appointments, and other compliance data are current as of that run.

Nothing. To refresh the data later, open the agency's detail page and re-run sync from there.

Red

Error

The sync failed. This covers both NIPR-side errors (NIPR returned an error response) and processing errors (the response could not be ingested).

Open the agency's detail page to see the error context, fix the underlying issue (most often a missing or invalid NPN), and re-run the sync. If the error persists, contact Turris support with the agency's NPN.

Neutral

Not Applicable

Compliance data sync isn't applicable for this agency — typically because there's no NPN to query NIPR with.

Add an NPN to the agency in the detail page if one becomes available, then sync.

Neutral

No Data

NIPR returned a response but no compliance data was found for the NPN.

Verify the NPN is correct in the agency's detail page. If it is, the entity may simply have no producer record on file with NIPR yet.

Frequently Asked Questions

Why are some of my branches missing from the table? The page lists every agency that has been added to your organization structure in Turris. If a branch is missing, it has not been onboarded yet. Reach out to your administrator or Turris support to add it.

Why doesn't the inline sync icon appear on some rows? The inline icon only appears for rows whose status is Not Started AND whose agency has an NPN on file. Rows already in Queued, Processing, Success, or Error never show the icon — re-sync those from the agency's detail page. Rows without an NPN cannot be synced at all.

The Actions menu is missing on some rows. Why? The row-level Actions menu is permission-gated. If your role does not allow reassigning or updating agents, the menu is hidden. Your administrator can grant the required permissions.

A DRLP badge is showing as +N. How do I see the full list? When an agency has more than three DRLPs, the first three are shown inline and the remaining count is collapsed into a +N badge. Click the +N badge to open a popover listing every additional DRLP. Each DRLP, whether inline or in the popover, links to that agent's detail page.

One agency failed during a bulk sync — did the rest fail too? No. Each agency in a bulk sync is processed independently. If one fails, the others still complete. The failed agency's row shows Error and the other rows continue moving through Processing to Success on their own schedule.

Can I cancel a sync once I've started it? Not from this page. Once a sync is queued, it will either complete or fail on its own. If a sync appears stuck in Processing for longer than a few minutes, contact Turris support with the agency's NPN.

Best Practices

  1. Onboard the top company first, then branches. This ensures the organization structure is fully established before you start retrieving compliance data, and avoids orphaned branches without a parent.

  2. Sync every branch in bulk on day one. Use the Actions → Sync Compliance Data workflow to bring the whole organization up to date in a single operation rather than syncing one row at a time.

  3. Assign DRLPs as soon as a branch is added. A DRLP is required for state-by-state license compliance and appointment management. Assigning early prevents downstream gaps when license filings depend on a designated person.

  4. Re-sync after licensing changes outside Turris. Whenever a new license is issued, an appointment terminates, or a regulator updates a record outside our system, run a fresh sync from the agency's detail page so the dashboard reflects the current state.

  5. Use the Sync Status filter to triage. Filter on Error to surface every agency that needs intervention. Filter on Not Started to find agencies that still need their first sync after onboarding.

Related Pages

  • Agency Detail Dashboard — Per-agency drill-down centered on an interactive United States license map, with tabs for alternate legal names by state and the full PDB report.

  • Legal Name by State — Tab on the agency detail page listing every alternate or historical legal name NIPR has on file, broken out by state and branch.

  • Agency Detail: PDB Report Tab — Tab on the agency detail page presenting a Producer Database-style compliance snapshot assembled from the most recent NIPR synchronization.

Need Help?

If you have questions about the Agencies page or encounter any issues, contact our support team at support@turris.com.

Did this answer your question?