Description:

Currently, when a Connector connection configured(e.g., SharePoint, Google Drive, or other third-party content connectors used to ingest knowledge sources into Atlassian Intelligence, search, and KB suggestions) becomes disconnected, broken, or stops syncing, there is no native notification or alerting mechanism to inform org admins of the disconnection.

Current Behavior:

• Connector connections at the Admin Hub level can silently break or stop syncing without any admin-facing alert or notification.

• Org admins must manually log in to the Admin Hub and verify each Connector connection on a daily basis to ensure they remain active and healthy.

• There is no email notification, in-product banner, or audit log entry surfaced when a Connector connection drops, fails authentication, or stops ingesting content.

• Downstream features that depend on ingested content (KB suggestions, search results, Rovo answers) silently degrade with no visibility to admins.

Expected Behavior:

• When a Connector connection in the Admin Hub is disconnected, broken, authentication fails, or sync stops, org admins should receive a proactive notification (email, in-product alert in Admin Hub, or both).

• The notification should include details such as: which Connector was affected (e.g., SharePoint, Google Drive), the connection name, when the disconnection was detected, and the suspected reason (auth failure, network, revoked permissions, etc.).

• Optionally, a periodic health-check summary of all Connector connection statuses in the Admin Hub would further reduce operational overhead.

• Ideally, a dedicated "Connector Health" dashboard view in the Admin Hub showing the live status of all configured connectors.

Business Justification:

• A broken Connector connection means content from third-party sources stops being ingested, causing KB suggestions, search results, and Rovo responses to silently degrade — agents and customers lose access to relevant knowledge without any visibility.

• Manual daily validation of Connector connections in the Admin Hub is not scalable and introduces unnecessary operational burden on org admins, especially in larger organisations with multiple connectors configured.

• Proactive alerting ensures faster remediation and maintains the integrity of the self-service, agent-assist, and AI-powered search/answer experiences.