---
title: "Settings health dashboard (post-onboarding)"
canonical: "https://support.appfire.com/space/FD/3435889217/Settings%20health%20dashboard%20(post-onboarding)"
format: markdown
---
> Macro (aura-html)

The Settings dashboard provides a centralized overview of data health, system integrations, and organizational user metrics to ensure high reporting accuracy. 

By monitoring the real-time status of connected repositories, projects, and tickets, you can quickly identify and resolve pipeline failures before they skew critical business metrics. 

Additionally, the dashboard tracks team structure, merge hygiene, and licensing data to optimize resource allocation and confirm that active contributor counts are accurate. 

Ultimately, this dashboard serves as a vital governance tool that safeguards data integrity and helps leadership make dependable, data-driven decisions.

> 📝 The Settings dashboard is accessible after your organization's [essential setup](https://appfire.atlassian.net/wiki/spaces/FD/pages/2833023493) is complete.

## Data health

The **Data health** section of the dashboard serves as an automated data-integrity auditor for engineering operations, tracking the health of integrations, repositories, PR projects, and ticket projects. Its core feature is real-time status tracking—categorizing connections as healthy, rate-limited, failed, or archived—which instantly flags syncing issues that could corrupt downstream reporting.

![Data health section on the Settings dashboard in Appfire Flow.](media://ca17c360-2162-402c-9284-a4512449c1bb)

Because metrics like commit velocity, pull request cycle times, and ticket completion directly dictate roadmaps and resource allocation, any data failure could lead to misleading reports and costly strategic errors. 

By providing a single pane of glass to monitoring these integrations, the dashboard enables teams to proactively detect and resolve pipeline disruptions, ensuring that engineering metrics remain accurate, reliable, and auditable.

To review your integrations, repos, PR projects, or ticket projects, click the **View all** button in the corresponding pane.

## Users and teams

The **Users and teams** section of the dashboard serves as an automated governance layer for organizational structure, focusing on unmerged users, team alignment, and license utilization. Its key features include monitoring team hygiene to ensure developers are correctly assigned, tracking pending user merges, and auditing active contributor counts against purchased licenses.

![Users and teams - Flow settings.png](media://83895445-3df5-4d10-b748-8c938f4095db)

This dashboard centers on operational efficiency, accurate cost accounting, and team performance tracking. Without proper team alignment, engineering metrics become skewed, making it difficult to measure the true capacity and productivity of specific cross-functional teams. 

Furthermore, by cross-referencing active contributors with available licenses, the dashboard prevents over-spending on underutilized software seats while ensuring that the organization remains fully compliant and optimized from a headcount and budget perspective.

## Quick links

The **Quick links** section lists direct links that serve as a contextual documentation and navigation layer.

![Quick links section on the Settings dashboard in Appfire Flow.](media://fb850b19-94a2-4dc1-83ec-d5183da09f7d)


> Macro (excerpt)
> 
> ## Data integrity
> 
> The Commit checker in the **Data integrity** section provides granular transparency by diagnosing exactly why a specific commit has been excluded from default reports, explicitly citing system rules or data anomalies. This acts as a vital auditing tool that removes the black box of automated metrics, giving data administrators the clear evidence needed to maintain total trust in organizational reporting.
> 
> ![Data integrity section on the Settings dashboard in Appfire Flow.](media://734c0c1e-fd70-4f95-89ad-f32b3a6b4b87)
> 
> To check whether a specific commit is currently included in your reports:
> 
> 1. In the **Commit SHA** field, enter the [commit’s SHA](https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits) (commit’s unique ID).
> 2. Click **Check commit**.
> 3. A result can display the following statuses:
>   1. **Commit not found** (Flow did not find a matching commit in the last 90 days)
>   2. **Included in reports** (Flow found the matching commit; the commit data is included in reports)
>   3. **Not included in reports** (Flow found the matching commit; the commit data is not included in reports)
> 
> ![Commit is not included in reports result modal.](media://5a321f31-bcac-42e2-ba8e-71cb70f8e9a2)
> 
> - **Status** - Displays commit check status. In case of the **Not included in reports** status, the result modal explicitly calls out the system logic explaining why a commit is not included in reports. In this example, the commit is flagged as a `merge_commit` under user exclusions and as an `is_outlier` since its impact is too large.
> - **Processing summary** - Tracks the deduplication status to show exactly how the data pipeline handled the commit.
> - **Associated user** - Provides an immediate context on who authored the work.
> 
> In addition, with the **Export as JSON** button, you can download the raw data payload for deep-dive troubleshooting or developer auditing.