Overview
Policy Licensing is the enterprise-wide license-compliance report that pulls every policy from every child member of your group into one searchable table. Use it to confirm that the agencies and agents writing your group's business hold the licenses required for each policy's risk state and product, and to drop into a child member's workspace to fix any policy that does not.
What is Policy Licensing?
Policy Licensing is where an enterprise licensing or compliance lead reviews license posture across every member of the group from one page, without opening each child member's account separately. For every policy, Turris evaluates the matched agency and matched agent against the licensing requirements for the policy's risk state and product, then shows a single overall compliance verdict.
Who uses it. Licensing managers, compliance officers, and operations leads at an enterprise upstream entity (a parent organization that owns multiple child upstream members). They reach for it during pre-audit reviews, monthly compliance close-outs, and ad-hoc checks triggered by a regulator inquiry or a non-compliant policy escalated by a member.
With Policy Licensing you can:
See every policy across every child member in one table, with no manual aggregation across organizations.
Choose the rule Turris uses to decide whether a policy is compliant: Either Agency or Agent, Agency Only, Agent Only, or Both Agency & Agent.
Save your preferred rule as the enterprise default so every member of your team sees the same verdict.
Narrow the report by child member, risk state, product, and compliance status.
Open a side panel on any policy to see the matched agencies and agents, the required license classes and lines of authority, and the licenses on file.
Read how each policy was matched to its agency, agent, and product, including whether the match was automatic, rule-based, or manual.
Jump into a child member's workspace to act on a non-compliant policy without losing your filters.
Download the report as CSV in up to three shapes: compliance verdicts, mapped target fields, or source data combined with the compliance report.
Accessing Policy Licensing
Open Left sidebar → Policy Licensing. The page stacks four elements from top to bottom:
The Compliance Mode bar: a slim bar with the label Compliance Mode, an information icon (the diagram and explanation open in a popover), and a four-way toggle on the right.
A highlighted banner directly under the bar, shown only when your selected mode differs from the saved enterprise default.
The filter bar: the Child Member, State, and Product dropdowns; the Status pills; the Include Expired badge; and the Export CSV button.
The policy table.
The table shows these columns:
Column | Description |
Policy Number | The policy identifier from your source data. Click the value to copy it to your clipboard. |
Child Member | The child member (upstream entity) the policy belongs to. |
Risk State | The U.S. state or territory where the insured risk sits. License compliance is evaluated against this state. Shown as a state circle plus the full state name. |
Product | The product in your catalog that the policy maps to. A yellow badge with an alert icon means the product is not yet matched, so licensing requirements cannot be determined; click it to open Policy Data and resolve the match. |
Carrier | The carrier reported on the policy, when available. Click to copy. |
Agencies | The matched agency or agencies on the policy. Each name is a colored badge keyed to that agency's license-compliance status (see Status Color Legend). |
Agents | The matched agent or agents on the policy, color-coded the same way. |
Status | The policy's overall compliance verdict under the current Compliance Mode. When a reason applies, an information icon appears on the badge; hover it for the exact reason. |
Match Reason | A short explanation of how the policy was matched to its agency, agent, and product. Hover for the full text. A small pill marks the source: Auto (matched by AI), Rule (matched by a deterministic rule), or Manual (matched by a person). |
(member-switch button) | A pill at the far right showing the child member's name with a right-arrow. Click it to drop into that member's workspace (see Switching Into a Child Member). |
When more than two agencies or agents are matched to a single policy, the first two show inline and a +N chip opens a popover with the rest.
Tip: Click anywhere on a policy row except the member-switch button at the far right to open the policy detail panel on the right side of the screen.
Note: A policy that carries more than one transaction can be expanded inline. The expanded child rows reuse the columns to show, left to right, the transaction type and date, the effective date, the expiry date, the premium, the aggregate coverage, and the source file the transaction came from.
Selecting a Compliance Mode
When you'd do this. Different lines of business and different regulators expect different licensing logic. Some require only the agency to be licensed; others require the producing agent specifically; others require both. The Compliance Mode tells Turris which rule to apply when it computes the Status column.
The four modes:
Mode | A policy counts as Compliant when |
Either Agency or Agent | Either the matched agency or the matched agent is compliant. This is the shipped default for new enterprises. |
Agency Only | Only the matched agency is evaluated. Agent compliance is disregarded. |
Agent Only | Only the matched agent is evaluated. Agency compliance is disregarded. |
Both Agency & Agent | Both the matched agency and the matched agent must be compliant. |
The control sits at the top of the page as a slim bar labeled Compliance Mode. Click the information icon next to the label to open a popover with a small diagram (two chips, Agency and Agent, joined by OR, AND, or a dash) and a one-line description of the selected mode, so you can confirm which side counts.
Changing the mode immediately recalculates the Status column for every policy. It is a calculation setting, not a row filter, so no rows disappear when you switch modes.
Overriding versus saving the default
The mode shown on first load is your saved enterprise default. When you pick a different mode here, two things happen:
A banner appears under the bar stating that you are overriding your saved default, and naming what that default is.
The mode you picked is stored in the page URL only. Refreshing or sharing the URL preserves it, but other team members keep seeing the saved default.
The banner offers two actions:
Reset to default clears the override and reverts the toggle to your saved enterprise default.
Save as new default persists the selected mode as the new enterprise default. Every member of your enterprise sees this mode the next time they load the page.
Note: Because the override lives in the URL, you can copy the page URL with your chosen mode and filters and send it to a colleague; they land on the exact same view without re-picking anything.
Filtering and Searching
The filter bar above the table narrows the report to the slice you care about.
Filter | Type | Purpose | Example use |
Child Member | Multi-select dropdown | Limits the report to one or more child members in your enterprise. | Reviewing only the East Coast subsidiary? Pick that member and ignore the rest. |
State | Multi-select dropdown | Limits the report to policies whose Risk State is one of the selected states. | Auditing California ahead of a CDI inquiry? Pick CA. |
Product | Multi-select dropdown | Limits the report to policies mapped to the selected products. | Reviewing E&O placements? Pick the E&O product to hide everything else. |
Status | Badge toggles (multi-select) | Six pills: Non-Compliant, Pending Data, Compliant, NPN Missing, NPN Invalid, Unresolved. None are selected on first load, so the report opens showing every status; toggle a pill to show only its rows (toggle several to combine them). | |
Include Expired | Single toggle badge | Sits to the right of the Status pills, next to Export CSV. Expired policies are shown by default; click the badge to exclude them, and click again to bring them back. The badge is highlighted while expired policies are included. |
Each dropdown supports Select All. The filters, the Compliance Mode override, and the Include Expired toggle are all stored in the URL.
The page also honors a free-text search value (the URL search parameter). It matches across Policy Number, Child Member, Risk State, Product, and Carrier at once, so a partial keyword like Trav is enough to surface Travelers policies.
Tip: To share the exact view you are looking at, for example a California non-compliant slice under Both Agency & Agent mode, copy the URL from the address bar and send it.
The Policy Detail Panel
When you'd do this. A policy shows up as Non-Compliant and you want to see which agency or agent failed, what license was required, and what license is actually on file before deciding who to contact.
Click anywhere on a policy row (other than the member-switch button) to slide the detail panel in from the right. The table collapses to a narrow strip on the left so you can keep clicking through rows without closing the panel. The panel is organized top to bottom.
Header
Shows the Policy Number in bold, the overall Status badge, and a question-mark popover that explains each status value. A close (X) icon sits at the top-right.
Policy metadata
A two-column grid showing Upstream Entity (the child member that owns the policy), Risk State (state circle plus full name), Product (when matched), Carrier (or a dash when missing), and Expiry Date.
Source Data
An expandable Source Data accordion. Open it to compare what the source file said against what Turris matched. It shows the raw source fields (insured entity name, producer name, producer code, license number), the entity and product matching status with match confidence, and the matched entities.
Transaction History
A Transaction History (N) accordion, where N is the number of transactions on the policy. Expand it to see each transaction (new business, renewal, endorsement, cancellation, audit, reinstatement, or bound) with its transaction date, effective date, expiry date, premium, aggregate coverage, and source file name.
Compliance summary
A one-line summary above the cards: how many matched agencies are compliant out of the total, and (when agents are matched) how many matched agents are compliant out of the total. For example: Agencies: 1/2 compliant Agents: 3/3 compliant.
Compliance detail
One card per matched agency followed by its matched agents. Each card shows the name and NPN, a compliance-status badge (Compliant, Missing License, Missing LOA, NPN Not Required, NPN Missing, or NPN Invalid), the Requirements (the license class and line of authority the policy's state and product demand), and the Relevant Licenses on file, color-coded by license state (Active, Expiring, Expired, Inactive).
Switching Into a Child Member
When you'd do this. A policy is non-compliant, and the actions that fix it (matching the agency or agent, requesting a license, contacting an agent, assigning a product to your catalog) live inside the child member's own workspace.
At the far right of every policy row is a pill button showing the child member's name with a right-arrow; hovering it reads Switch to [member name]. Click it and Turris will:
Carry your current Include Expired, Status, State, and Product filters forward in the URL.
Re-authenticate you into the child member's organization.
Land you on that child member's own Policy Licensing page with the same filters already applied.
To return to the enterprise view, use the organization switcher in the top navigation.
Note: Only one organization switch can run at a time. While one member-switch button is loading, every other switch button on the page is disabled.
Exporting to CSV
When you'd do this. You need the compliance report outside Turris, for an auditor, a regulator filing, or your own records.
Click Export CSV (to the right of the Include Expired badge) to open a menu with two or three options, depending on what is on file for your enterprise:
Export | Contents |
Compliance Report | License compliance status for every policy, agency, and agent in the current view. |
Mapped Data | Only the mapped target fields for each transaction, without source columns. |
Mapped Transaction Data | Every transaction with its source columns and the policy's compliance details (agency, agent, status), repeated per transaction. Shown only when your enterprise has full per-transaction source data on file. |
The export runs in the background. After you pick a type, Turris confirms with a toast that names the email address the download link will be sent to ("Your export is being generated. We'll email a download link to [your email] when it's ready."). The file honors the current Compliance Mode and Include Expired toggle, so it matches what is on screen.
Note: The link arrives by email rather than downloading immediately, because the cross-member report is computed in the background. Check the inbox for the account you are signed in with.
Status Color Legend
Agency and agent badges in the Agencies and Agents columns (and on the detail cards) are colored by that entity's license-compliance status for the policy's state and product:
Color | Label | Meaning | What to do about it |
Green | Compliant | The entity holds an active license in the required class with the required line of authority. | No action. |
Red | Missing License | The entity holds no license in the required class for this state and product. | Open the child member workspace and either attach the missing license or start a license request. |
Yellow | Missing LOA | The entity holds the required license class but is missing one or more required lines of authority. | Open the child member workspace and add the missing line(s) of authority to the existing license. |
Yellow | NPN Missing | The entity requires an NPN to verify licensing, but none is on file. | Add the entity's NPN in the child member workspace so its licenses can be checked with NIPR. |
Yellow | NPN Invalid | NIPR could not find a record for the entity's NPN, so the NPN on file is likely wrong. | Correct the NPN in the child member workspace and re-sync. |
Grey | NPN Not Required | The agency is exempt from license evaluation (for example a sole proprietorship in a state that does not require an agency NPN). Hover the info icon to confirm. | No action. The entity is shown for context but is not graded. |
Grey | External / Unmatched | The name appears in the source data but is not registered in Turris or could not be matched. Hover the info icon to confirm. | Open the child member's Policy Data view to investigate the match. |
Overall policy Status badges in the Status column use their own set of values. When a reason applies, an information icon appears on the badge; hover it for the precise reason.
Color | Label | Meaning | What to do about it |
Green | Compliant | Every matched pair on the policy passes the rule set by the current Compliance Mode. | No action. |
Red | Non-Compliant | At least one matched agency or agent fails for the current Compliance Mode. The reason names which side and how: Agency Missing License, Agency Missing LOA, Agent Missing License, Agent Missing LOA, or Agency & Agent Both Fail. | Click the row to open the detail panel, then use the member-switch button to act inside the child member's workspace. |
Blue | Pending Data | The matched agency or agent has been matched but is awaiting NIPR data ingestion. The reason names which side is pending: agency, agent, or both. | No action. Compliance is re-evaluated automatically once the licensing data arrives. |
Yellow | NPN Missing | A matched agency or agent that requires an NPN has none on file, so its licensing cannot be checked. | Add the missing NPN in the child member workspace; this does not resolve on its own. |
Yellow | NPN Invalid | NIPR rejected a matched agency's or agent's NPN, so the NPN on file is likely wrong. | Correct the NPN in the child member workspace and re-sync; this does not resolve on its own. |
Grey | Unresolved | Compliance cannot be determined yet. Either the policy's product is not matched to your catalog, or every matched agency is NPN-exempt and no agent is matched. | If the product is unmatched, click the yellow product badge to open Policy Data and match it. If an agent is missing, match an agent in the child member workspace. |
License badges on the detail panel's Relevant Licenses use four states: Active (green), Expiring (yellow), Expired (red), and Inactive (grey).
Frequently Asked Questions
Why is the table empty when I open the page? Policy Licensing aggregates data from every child member's policy data. If no child member has ingested policy data, the page shows "No policies found." If your current filters exclude every policy, the table reads "No policies match the current filter." Clear your filters and confirm that at least one child member has uploaded transactions on their own Policy Licensing or Policy Data page.
Why does a policy show Non-Compliant even though I can see a licensed agency on it? The verdict depends on the selected Compliance Mode. In Agent Only mode the agency's licenses are ignored; in Both Agency & Agent mode both sides must pass. Switch the Compliance Mode at the top of the page and the same policy may evaluate differently.
What does the yellow badge on the Product column mean? That product is not matched to your enterprise's product catalog. Turris cannot evaluate licensing without a matched product, so the policy's Status is Unresolved. Click the yellow badge to open Policy Data, then run matching or assign the product manually for the relevant child member.
What does Pending Data mean? The matched agency, agent, or both have been identified, but their license records from NIPR are still being ingested. No action is required; Turris re-evaluates the policy automatically once the data is on file. The badge tooltip tells you which side is pending.
What is the difference between NPN Missing and NPN Invalid? NPN Missing means a matched party that requires an NPN has none on file, so its licensing cannot be checked. NPN Invalid means NIPR rejected the NPN that is on file, so it is likely wrong. Neither resolves on its own: add the missing NPN, or correct the invalid one and re-sync.
Does changing the Compliance Mode here affect my colleagues? No. A change on this page is a session-only override stored in the URL. Other members of your enterprise keep seeing the saved default until you click Save as new default in the override banner.
Where does the CSV export go? The report is generated in the background and a download link is emailed to the address on your account. A confirmation toast names that address when you start the export.
Best Practices
Set the Compliance Mode that matches your operating rule and save it as the default. The shipped default is Either Agency or Agent. If your business requires stricter logic, pick the mode your auditors think in and click Save as new default so every member of your enterprise starts from the same verdict.
Triage with the Status pills. No status is pre-selected, so the page opens showing everything. Toggle Non-Compliant to work the policies that need action first, then NPN Missing and NPN Invalid for data problems that will not fix themselves. Leave Pending Data for last, since those resolve automatically as NIPR data arrives.
Resolve product-match issues from the Policy Data page. When a yellow product badge appears in the Product column, click it to open Policy Data, then run matching or assign the product manually for the relevant child member. Once the product is matched, the policy's Status updates the next time the page loads.
Use the compliance summary in the detail panel before switching. Before you switch into a child member, open the detail panel and read the
Agencies: X/Y compliant Agents: A/B compliantline. It tells you whether the problem is on the agency side, the agent side, or both, so you know what to fix once you land.Share filtered URLs to align on a slice. Every filter, the Compliance Mode override, and the Include Expired toggle live in the URL. Copy the address bar and send a colleague the exact view, instead of describing it.
Need Help?
If you have questions about Policy Licensing or encounter any issues, contact our support team at support@turris.com.