Notifications dashboard

The Admin console dashboard includes a Notifications panel that surfaces issues and system messages that require admin attention. This panel provides a centralized view for connector health problems and high-priority alerts. Admins can identify broken or at-risk components immediately upon opening the console.

The Notifications panel empowers admins by providing immediate clarity and control over connector health. This feature directly addresses the following challenges:

• Verified readiness: Admins now receive clear indicators when a new connector is ready for testing in search and chat, eliminating guesswork after initial connection.
• Proactive health monitoring: Instead of silent failures, Glean surfaces real-time status updates and prescriptive troubleshooting steps. This allows admins to resolve issues independently and quickly.

This streamlined communication reduces reliance on manual support and ensures your Glean deployment remains healthy and high-performing.

The dashboard also shows suggestions. The Tools tab links to unfinished or available connector and tool setup. See Setup suggestions. The Connectors tab recommends apps that people use but that Glean doesn't connect to yet. See Connector suggestions.

Setup suggestions

A suggestion is setup guidance, not an alert. It points to a step you haven't started or finished. Connector health issues, such as failing credentials, appear in the Notifications panel.

The Tools tab in the dashboard's Suggestions section lists up to three connector setup steps to start or finish. Each suggestion names a connector and links to the page where you can complete the step. When browser extension usage data is available, Glean lists steps for apps that more people use first. Otherwise, the order doesn't indicate priority.

Suggestions reflect your current setup each time the dashboard loads. When you finish a step, its suggestion disappears, and another suggestion may take its place.

Suggestion types

Glean checks each connector in your deployment and shows at most one suggestion per connector.

Suggestion	When it appears	Button	Destination
Finish setting up connector name	You started adding the connector but haven't finished its setup.	Continue setup	The connector's setup page.
Finish setting up tools for connector name	The connector is set up, and a tool or MCP server connected to it hasn't finished setup.	Continue setup	The connector's Tools tab, or the setup page for that tool or MCP server.
Set up tools for connector name	The connector is set up and has no tools yet, but Glean offers tools or an MCP server for it.	Set up tools	The connector's Tools tab, or a new tool or MCP server setup form. Confirm the connector in the form before you save.

The connector name matches the name shown in Connectors. If a tool or MCP server is shared by more than one connector, Glean suggests finishing it only once.

When the Tools tab shows no suggestions

The Tools tab can show one of these messages instead of suggestions:

• Loading tool setup suggestions… — Glean is still checking your connector and tool setup.
• Unable to load tool setup suggestions. Please try again later. — Glean couldn't check your setup. Reload the dashboard later.
• No tool setup suggestions — Glean didn't find a setup step to suggest right now.

None of these messages confirms that every connector and tool is fully set up. Glean skips a connector when it can't determine the setup status, for example when a tool isn't linked to a specific connector or doesn't report whether its setup is finished. To review setup for a specific connector, open it in Admin console → Connectors.

Connector suggestions

The Connectors tab in the dashboard's Suggestions section recommends apps to connect to Glean. It lists apps that people at your company use but that no connector in your deployment covers yet. After you connect an app, people can search and get answers from its content in Glean.

To see connector suggestions, open the Admin console dashboard and select the Connectors tab in the Suggestions section.

How Glean chooses connector suggestions

Glean bases connector suggestions on Glean browser extension activity, not on all employee activity. Apps that people use only without the extension don't count toward a suggestion. To increase coverage, deploy the extension to managed devices. See Deploy the browser extension to managed devices.

An app appears in the Connectors tab when it meets every condition:

• At least 10 people used the app with the browser extension in the last 30 days.
• No connector in your deployment covers the app. A connector covers its app even if you haven't finished setting it up. To continue unfinished connector setup, use the Tools tab. See Suggestion types.
• Glean offers a connector for the app that you can add to your deployment.

The tab shows up to three apps, with the most used app first. The order changes as usage changes.

Connect a suggested app

Each suggestion shows:

• Connect app name — the app to connect
• A description explaining that people use the app but it isn't connected yet
• Used by N people in X days — how many people used the app with the extension, and on how many days Glean has usage data in the last 30 days. Those days aren't always consecutive.

To connect the app, click Connect. Glean opens the app's connector setup page. If the app belongs to a connector suite, the suggestion depends on whether the suite is set up:

• If the suite isn't set up, the suggestion names the suite and opens its setup page.
• If the suite is already set up, the suggestion names the app and opens the suite's connector page, where you add the app.

After you add the connector, the app no longer appears in the Connectors tab, even before you finish setup.

When the Connectors tab shows no suggestions

The Connectors tab can show one of these messages instead of suggestions:

• Loading connector suggestions… — Glean is still checking app usage and your connectors.
• Connector suggestions need recent browser extension app usage, which isn't available yet. — Glean doesn't have recent usage data, so it can't tell which apps to suggest. Usage data can be missing on a new deployment, before the browser extension reports activity, or out of date when Glean hasn't refreshed it in the past few days. This message doesn't mean that no apps qualify.
• No connector suggestions — Glean has recent usage data and didn't find an app that meets the criteria in How Glean chooses connector suggestions.

Connector suggestions don't report connector health. Problems with apps you've already connected, such as failing credentials, appear in the Notifications panel.

Notifications

The Notifications panel follows the Suggestions section on the dashboard. Each row represents a single notification. Glean groups these in a scrollable list ordered by recency.

Notification components

Each notification card provides a concise and actionable summary:

• Title: Summarizes the issue, such as Failing credentials: Slack or Failing credentials: Freshdesk.
• Description: Explains the error and its impact, such as degraded search results due to access failures.
• Recommended action: Instructs the admin to review failed checks and follow the linked documentation.
• Status and recency: Indicates how long ago the issue occurred and includes an unread indicator blue color dot for new items.
• Fix issues: Provides a Fix now button that navigates directly to the affected connector or configuration page.
• Overflow menu: Allows the admin to Mark as unread or Delete the notification.

Filter notifications by severity

The Notification type menu allows you to filter the list by severity. You can toggle the following categories independently:

• Critical: Focuses on alerts that directly affect data freshness, search completeness, or core system health.
• Warning: Surfaces urgent issues that do not yet break core functionality.
• Info: Displays informational updates or low-priority system messages.

How dashboard notifications relate to alerts

Dashboard notifications are powered by the same health checks and alerting framework that drives email-based admin alerts and the Alerts settings page.

Conceptually:

• The Dashboard Notifications panel is the in-product view: a live list of active issues that impact search quality, data freshness, or connector health.
• The Alerts page (Admin console → Notifications → Alerts) is where admins configure recipients and behavior for email-based alerts.
• Email alerts remain the push channel. Dashboard notifications are the always-available, pull-based view when an admin is already in the console.

If a connector credentials check fails, admins can expect:

• A notification card on the Dashboard that summarizes the failing connector and links to the relevant troubleshooting article.
• An email alert (depending on alert configuration) sent to the recipients defined under Alerts.

Admin notifications are designed to be the first place admins look when they want to understand the current health of their deployment and quickly drill into the highest-impact issues.

For more information on alerts, see About Admin Alerts.