---
sourceDocument: Australia Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/impact

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Team Lead dashboard

# Scan Engine Team Lead dashboard {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Scan Engine Team Lead dashboard

The Scan Engine Team Lead dashboard is designed for team leads to monitor and manage scan findings and technical debt within their development teams.
It provides a comprehensive view through various overview modules and trend charts that track development time needed to resolve issues, exceptions awaiting approval, and the overall health of the codebase as assessed by the Scan Engine.
Show full answer Show less  

## Key Features

* **Overview Modules:** Display critical metrics such as total team technical debt (development time required to fix findings), unapproved exceptions, health score (percentage of definition occurrences without findings), number of active scan engine definitions, technical debt by category, and open findings by developer.
* **Trend Charts:** Visualize historical data for technical debt, technical debt by developer, policy-prioritized findings, findings ranked by impact and effort, findings by developer and category, real-time preventions, unapproved exceptions, and update sets. These charts help prioritize work and track team performance over customizable time periods.
* **Interactive Elements:** Team leads can filter developers, approve or reject exceptions directly from the dashboard, and drill down into detailed views of findings and policies.
* **Role-Based Access:** Usage requires either the *impact.development.team.lead* or *impact.app.admin* role, ensuring data visibility is scoped to appropriate team leads and admins.

## Data Sources and Practical Use

The dashboard pulls data from specific Scan Engine tables such as *snsesummaryscandetail* , *snseexceptionreason* , *snsescanresult*, and others. Each overview module and trend chart is backed by these data sources to provide accurate and actionable insights. The data shown is limited to team members under the defined team lead, enabling focused management and accountability.

## Benefits for ServiceNow Customers

* Allows team leads to efficiently track and reduce technical debt across their team, improving code quality and maintainability.
* Enables timely review and management of exceptions, ensuring compliance with policies.
* Helps prioritize remediation efforts by highlighting findings with the highest impact and the lowest resolution effort.
* Supports proactive prevention by monitoring real-time preventions where findings are blocked before saving.
* Facilitates performance tracking of individual developers and overall team health, assisting in resource planning and coaching.  
The Team Lead dashboard includes trend charts and the following overview modules.
{#scan-engine-team-lead-dashboard__table_hrx_lll_fhc__entry__2}

| Information module | Description |
|-|-|
| Total team technical debt | The amount of development time required to resolve all findings for the team. |
| Unapproved exceptions | The number of exceptions currently waiting to be approved or rejected. |
| Health score | The health score represents the percentage of definition occurrences used across the platform that did not return any findings. It is calculated as: `(1 - (F / D)) * 100` Where F is the number of findings, and D is the number of definition occurrences. "Definition occurrences" refers to the total number of times a definition has been executed by the Scan Engine to generate findings. |
| Active scan engine definitions | The number of definitions currently being used by the Scan Engine. |
| Technical debt by category | The estimated amount of development time required to resolve all findings within each category for the entire team. |
| Open findings by developer | * All open findings sorted by each developer on the team. * The value in the center is the total number of open findings for all selected developers. * Select a name to add or remove the developer from the chart. {#scan-engine-team-lead-dashboard__ul_irx_lll_fhc} |
[Table 1. Team Lead dashboard overview]

{#scan-engine-team-lead-dashboard__table_hrx_lll_fhc}

## Team Lead trend charts {#scan-engine-team-lead-dashboard__section_mdb_tll_fhc}

The Team Lead dashboard includes the following trend charts.
{#scan-engine-team-lead-dashboard__table_t33_wll_fhc__entry__2}

| Chart | Description |
|-|-|
| Technical debt | * The amount of development time required to resolve all findings for the team. * You can customize the time period using the date selector. {#scan-engine-team-lead-dashboard__ul_u33_wll_fhc} |
| Technical debt by developer | * A developer's total technical debt, represented as the estimated amount of development time required to resolve all their findings. * You can configure the developers displayed in this chart in the Scan Engine properties. {#scan-engine-team-lead-dashboard__ul_w33_wll_fhc} |
| Policy prioritized findings | * Findings that have a Priority status within a policy. To view the policy, select the name in the policy column. * Select View all findings to view the list in a separate tab. {#scan-engine-team-lead-dashboard__ul_y33_wll_fhc} |
| Findings by impact to instance | * Findings listed in order of highest impact to your instance with the lowest time to resolve. Address these findings first to get the highest impact with the lowest effort. * Select a finding number to view it in a new browser window. {#scan-engine-team-lead-dashboard__ul_aj3_wll_fhc} |
| Findings by developer | * The number of findings by developer, classified by category. * Select a table entry to view the list of findings for a given developer in a new tab. {#scan-engine-team-lead-dashboard__ul_cj3_wll_fhc} |
| Real time preventions | * All real-time preventions by the team, for the selected time period. A real-time prevention is when the Scan Engine prevents a finding from being saved. * You can customize the time period using the date selector. {#scan-engine-team-lead-dashboard__ul_ej3_wll_fhc} |
| Unapproved exceptions | * All requested exceptions, by developer, requiring the team lead's approval or rejection. * Select the box to the left of an exception to approve or reject it * Select a Source record entry to view it for an exception. {#scan-engine-team-lead-dashboard__ul_gj3_wll_fhc} |
| Real time preventions trend | * All real-time preventions by each team developer, for the selected time period. A real-time prevention is when the Scan Engine prevents a finding from being saved. * You can customize the time period using the date selector. {#scan-engine-team-lead-dashboard__ul_jj3_wll_fhc} |
| Update sets | * All current update sets for the configured instance over the selected time period. * You can customize the time period using the date selector. * To filter the list, select the filter in the column heading. * You can add and configure instances from the My SN Instances related list in the Scan Engine properties. {#scan-engine-team-lead-dashboard__ul_lj3_wll_fhc} |
[Table 2. Team Lead dashboard trend charts]

{#scan-engine-team-lead-dashboard__table_t33_wll_fhc}

## Team Lead dashboard data sources {#scan-engine-team-lead-dashboard__section_jpj_1r4_nhc}

The following tables show the data source for each overview module and trend chart in the Team Lead dashboard.  
Note:  
All components require either the impact.development.team.lead or impact.app.admin role to use.
{#scan-engine-team-lead-dashboard__table_fwz_hr4_nhc__entry__2}

|   |   |
|-|-|
| Total team technical debt | sn_se_summary_scan_detail |
| Unapproved exceptions | sn_se_exception_reason |
| Health score | sn_se_scan_result |
| Active definitions | sn_se_definition |
| Tech debt by category | sn_se_summary_scan_detail |
| Open findings by developer | sn_se_summary_scan_detail |
[Table 3. Team Lead overview data sources]

{#scan-engine-team-lead-dashboard__table_fwz_hr4_nhc} {#scan-engine-team-lead-dashboard__table_gf1_jr4_nhc__entry__2}

|   |   |
|-|-|
| Technical debt | sn_se_summary_scan_detail |
| Technical debt by developer | sn_se_summary_scan_detail |
| Policy prioritized findings | sn_se_finding |
| Findings by impact to instance | sn_se_summary_scan_detail |
| Findings by developer | * sn_se_summary_scan_detail * sn_se_finding {#scan-engine-team-lead-dashboard__ul_hrt_4cp_nhc} |
| Real time preventions | sn_se_onsubmit_prevention |
| Unapproved exceptions | sn_se_exception_reason |
| Update sets | sn_se_scan_result |
| Real time preventions trend | sn_se_summary_scan_detail |
[Table 4. Team Lead trend chart data sources]

{#scan-engine-team-lead-dashboard__table_gf1_jr4_nhc}  
Note:  
The Team Lead dashboard charts only include data for members underneath the defined team lead.

