empowsec Reporting Dashboards: Metrics That Drive Action

Most security awareness platforms generate data. The challenge is turning that data into a signal that prompts action - knowing not just that the last phishing campaign had a 12 percent click rate, but which department drove that number, whether it is trending up or down, and which employees still have outstanding training assignments. empowsec reporting dashboards are designed to answer those follow-up questions directly, without requiring a separate report to be run or a data export to be processed. Everything lives in one place, filterable by the dimensions that matter, and the same data is available through the API for teams that want to pull it into their own tools.

This article covers what empowsec's reporting dashboards show, how filtering works, what resellers can see across their managed companies, and how the API extends reporting into external environments.

What the Dashboards Cover

empowsec reporting spans three domains: training completion, phishing simulation results, and risk scores. These are not separate standalone views that require navigating between different sections; they are connected dimensions of the same underlying data, and the dashboard design reflects that connection.

Training completion reporting shows which employees and departments have completed their assigned courses, what their pass scores were, how many assignments are outstanding, and which are overdue. For compliance purposes, this view answers the core auditor question: did the employees who were required to complete training actually do so, and when? Completion rates can be viewed per department to identify groups that are lagging, and individual records show the specific score each employee achieved on each course.

Phishing simulation reporting covers the full event spectrum from a campaign: how many emails were sent, what percentage were opened, what percentage resulted in a link click, what percentage resulted in credential submission on the landing page, and what percentage of employees proactively reported the simulation rather than interacting with it. Each of these percentages has a different implication for security posture, and seeing them side by side makes that implication clear. A high open rate combined with a low click rate suggests the campaign is visible and employees are evaluating it correctly. A high submission rate combined with a low report rate suggests both susceptibility and a weak reporting culture - two problems that call for different interventions.

Risk score reporting shows individual employee scores, department aggregates, and company-level trends over time. Because risk scores incorporate time decay, tracking the trend over a period of months is more informative than a point-in-time snapshot. A company whose average risk score has been declining steadily over six months is demonstrating genuine improvement in security behavior, not just improvement on a specific campaign. That trend data is what distinguishes a program that is working from one that is producing isolated data points.

Filtering: The Right View for the Right Audience

Raw metrics at the company level are useful for executives. They are less useful for a department manager who needs to know which of her twenty team members have not completed their assignment, or for a security analyst who wants to understand the phishing click behavior of a single user across multiple campaigns. empowsec reporting dashboards support filtering by individual user, by department, or across the whole company, so the same underlying data set serves each of these audiences at the appropriate level of detail.

Filtering by department lets a manager or administrator see completion rates, phishing outcomes, and risk scores scoped to a single team. This is particularly valuable when departments have different training requirements - a finance team with stricter compliance obligations, for example, or a newly hired group undergoing onboarding training. Rather than scanning a company-wide list to find the relevant rows, a department filter immediately focuses the view on the data that matters for that specific context.

Filtering by individual user gives security teams the ability to review the complete training and phishing history of a specific employee. This is useful in a number of situations: when an employee has been flagged for repeated phishing failures, when a manager requests a status check on a new hire, or when preparing the evidence needed to confirm that a specific individual has met their training obligations for the current compliance period.

These filters work across all three reporting domains simultaneously. Applying a department filter does not just narrow the completion view; it narrows the phishing results and risk score view as well, so a manager can see a coherent picture of their team across all dimensions without switching context.

Reseller Reporting Across All Managed Companies

For managed service providers and resellers who manage multiple client companies through empowsec, reporting does not stop at the single-company boundary. Resellers can view reporting data across every company they manage from within the reseller console. This cross-company view gives an MSP the ability to compare the security posture of different clients, identify which clients are lagging on training completion or showing high phishing click rates, and prioritize where to direct attention and resources.

This cross-company reporting is particularly valuable for MSPs that have made security awareness training a core part of their service offering. Being able to show clients consolidated reporting data - or to use it internally to identify clients who need a proactive outreach - is part of delivering a managed security awareness program rather than just providing software access. The reporting layer is what turns empowsec from a tool clients use into a service MSPs can actively manage and demonstrate value from.

API Access for BI and SIEM Integration

Not every organization wants to view security awareness data exclusively in empowsec. Many teams have invested in business intelligence tools, security information and event management platforms, or custom dashboards that aggregate data from multiple security systems. empowsec's reporting data is available through both the company API and the reseller API, so it can flow into any of these external environments.

This API availability means that training completion rates, phishing simulation results, and risk scores can be combined with other data sources in a BI tool to produce the specific view a particular organization needs. A CISO who wants to see security awareness metrics alongside patch compliance rates and access review completion in a unified dashboard can pull all three data sets into their tool of choice. An MSP that produces monthly client security reports can automate the data pull rather than manually exporting from empowsec each time.

The API approach also future-proofs the reporting investment. As an organization's data infrastructure evolves, the reporting data from empowsec can follow it without requiring the organization to change how they run their security awareness program. The data is available when and where it is needed, in the format that existing tools can consume.

What This Means for Your Team

• Three reporting domains - training completion, phishing simulation results, and risk scores - are consolidated in one dashboard rather than fragmented across separate tools.
• Filtering by user, department, or company means each stakeholder sees the view relevant to their scope, from an individual employee's history to a company-wide executive summary.
• Resellers can report across all managed companies, making empowsec a foundation for a managed security awareness service rather than just software access.
• API access for both company and reseller accounts lets reporting data flow into BI tools, SIEM platforms, and custom dashboards without manual exports.
• Trend data over time - especially for risk scores - shows whether a program is producing sustained behavior change, not just point-in-time campaign results.