The Browser Defender Dashboard is the page that provides administrators with a centralized, real-time view of your company's browser security posture, with details for each individual user. It is a monitoring and reporting page: protection configuration takes place in Setup, while each type of alert is explored in its own dedicated page. To access it, open Browser Defender from the side menu and select Dashboard. It requires Browser Defender to be active for your company and the Platform Administrator role; a user's data appears after the extension is deployed.
What this page is for
This page allows you to:
- Get a snapshot of your entire company's browser security posture — extension adoption, risky browsing, dangerous downloads, password reuse, and unmanaged extensions — at a glance.
- Analyze the protection status and event history of a single user through the Data per user table, then open their detail page.
- Compare a shorter or longer reporting window (Timeframe) before deciding whether a spike requires action.
This page is not intended for:
- Configuring protections, blocklists, or AI-based phishing detection — see Setup section.
- Analyzing or managing individual alerts in detail — see dedicated pages Browsing Alerts, Dangerous Downloads, Password Reuse, or Extension Governance.
- Deploying the browser extension to new users — see Setup / Users sections.
The Timeframe and summary cards
The Timeframe selector sets the reporting window: 2 Weeks (default), 1 Month, 3 Months, 6 Months, or 1 Year. It applies to all page widgets except extension status counts, which always reflect the current day's situation (see Extension Status).
The five summary cards provide an immediate overview: where available, hovering over them reveals sub-indicator details; clicking opens the dedicated page for that card.
| Users with active extension | Users whose extension has synced the corporate password (full protection) plus users with active extension but password not yet synced; hovering shows the breakdown. A separate row shows users with inactive extension (disabled by the user, or not detected for over 30 days). |
| Browsing alerts | Visits to sites flagged as malicious or high-risk, via threat-intelligence feeds, your company's blocklist, or AI-based analysis (can be enabled in Setup). Sub-indicators: pages visited despite the warning; distinct users with at least one alert. |
| Dangerous downloads alerts | Files that triggered a security warning during download. Sub-indicators: files downloaded despite the warning; distinct users with at least one alert. |
| Password reuse alerts | Cases where a corporate password was reused on an external site. Sub-indicators: alerts on a domain the user marked as safe; distinct users with at least one alert. |
| Third-party extensions detected | Total number of third-party extensions detected in your company; this card shows no additional sub-indicators (for detailed analysis see Extension Governance). |
The Data per user table
The Search field filters the table by first name, last name, or email; clicking a column header sorts the list by First Name, Last Name, Email, or Events (the sum of the four event counters). Clicking a user's email opens their detail page.
Available columns: First Name, Last Name, Email, the extension Status chip, and a counter for each of the four events: Browsing alerts, Dangerous downloads, Password reuse, DLP alerts (DLP, Data Loss Prevention: warnings about corporate data shares to unauthorized destinations detected by the extension; has no dedicated summary card — the summary cards remain five).
Extension Status
The Status chip indicates the extension situation for each user:
| Active | The extension is installed, responding correctly, and has synced the user's corporate password: all protections are active. |
| Active w/o password | The extension is deployed but has not yet synced the corporate password: password reuse alerts cannot trigger for this user until it does. |
| Last seen +30 days ago | The extension has not communicated with the backend for over 30 days (for example, due to extended absence or because the browser is no longer in use). |
| Disabled by user | The user has manually disabled the extension's protections; Setup determines whether this is allowed for end users. |
| Never installed | No extension has been detected for this user. |
Settings managed in other pages
Some elements that affect the data shown on this page are configured elsewhere:
- Extension deployment — whether users have installed/activated the extension depends on Setup and the extension itself.
- AI-based phishing detection — can be enabled at the company level in Setup > Preferences > Advanced Settings; if disabled, the Browsing alerts card shows a warning banner.
- Company blocklist/allowlist — URLs and domains blocked or allowed by your company are configured in Setup.
- Third-party extension policy — is reviewed and managed in Extension Governance.
Data updates
Changing the Timeframe, typing in the Search field, or clicking a column header updates the page immediately. A newly created user, however, may not appear right away: user records are synced on their own schedule, and once synced, their extension status and event counters begin populating as the browser is used.
NOTE: extension Status counts always reflect the current day: changing the Timeframe will never move a user between extension states — only the alert cards and event counters in the Data per user table respond to the Timeframe.
Troubleshooting
| Symptom | Likely cause | Solution | Escalation |
| A newly added user does not appear in the Data per user table | User records have not been synced yet | Check again the next business day | Contact support if the user is still missing after one business day |
| A user shows "Never installed" despite having the extension | The extension has not yet sent its first status update, or deployment is incomplete | Check deployment status in Setup / Extension Governance | Contact support |
| Extension Status counts do not change when selecting a longer Timeframe | Status counts always reflect the current day; only alert cards and event counters respond to the Timeframe | Compare the four alert cards across different Timeframes instead | — |
| The page shows "Activate Browser Defender" instead of data | Browser Defender is not active for this company | Contact LibraCyber to verify plan/activation | Contact support |
| The third-party extension count seems higher than expected | The counter includes every detected extension, not just risky ones | Consult the detailed list in Extension Governance | — |