> For the complete documentation index, see [llms.txt](https://docs.aisera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisera.com/aisera-platform/adding-data-to-your-tenant/integrations-and-data-sources/creating-a-connector/configuring-credential-expiration-alerts.md).

# Configuring Credential Expiration Alerts

Credential notifications alert tenant Admins when integration credentials are nearing expiration or have failed authentication, so they can re-authenticate before bots stop working. Configuration happens at two levels: global settings that apply to all integrations, and optional per-integration overrides for integrations that need a different cadence, known expiry date, or different recipients.

## How credential notifications work

When an integration's credentials expire or fail authentication, the integration stops working silently. Bots that depend on it fail, data ingestion stops, and end users experience disruption, often before anyone on the admin team is aware of the problem. Credential notifications close this gap by sending proactive and reactive email alerts to tenant Admins so they can re-authenticate before users experience disruption.

The Aisera Platform supports two categories of alerts. Proactive alerts warn Admins in advance when credentials are approaching a known expiry date, using a reminder schedule configured per integration. Reactive alerts fire when authentication fails at runtime. For example, the Aisera Platform generates an alert when an expired token causes a bot action to fail, when an OAuth token cannot be refreshed, or when a test-connection attempt is rejected.

The Aisera Platform delivers alerts as email digests on a daily or weekly cadence. For critical failures that should not wait for the next digest, a separate option sends immediate alerts outside the scheduled window.

The Aisera Platform splits credential notification configuration across two areas of the Admin UI. Global settings, found under **Settings > Configuration > Credential Notifications**, define the default behavior for all integrations in the tenant: who receives alerts, how often, and which event types trigger them. Per-integration settings, found in the **Notifications** section of the **Edit Integration** window, let Admins fine-tune behavior for a specific integration: setting a known expiry date, choosing a reminder schedule, or routing alerts to a different team. Per-integration settings are optional; integrations inherit the global configuration by default.

## Configure global notification settings

Global settings define the default notification behavior for every integration in the tenant. Configure these first.

1. Go to **Settings > Configuration > Credential Notifications**.
2. Select the **Enable Integration Credential Notifications** checkbox.
3. Under **Recipient Emails**, click **Add New** and enter each recipient email address. If left blank, the Aisera Platform sends notifications to all tenant Admins by default.
4. Under **Failure Digest Frequency**, select **Daily** or **Weekly**. 

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>If you select <strong>Weekly</strong>, a second dropdown appears next to the frequency selector. Choose the day of the week on which digests should be sent. Available days are Monday through Sunday. </p></div>
5. Under **Notification Types**, select each credential event type that should generate alerts. You can select any combination of the following:
   * **Proactive expiration reminders**: before credentials expire, based on the known expiration date configured per integration
   * **Credential already expired**: when credentials have passed their expiration date
   * **Auth failure at runtime**: when an integration fails authentication during bot execution
   * **Auth failure during ingestion**: when an integration fails authentication during data ingestion
   * **OAuth refresh-token failure**: when an OAuth token cannot be refreshed
   * **mTLS / certificate validation failure**: when a mutual TLS or certificate validation check fails
   * **Include test-connection failures**: to extend alerts to failed test-connection attempts
6. Optional: Select **Send immediately for critical events** to receive alerts outside the digest schedule when a critical credential failure occurs. Critical events include credentials already expired, OAuth refresh-token failure, and mTLS / certificate validation failure.
7. Click **OK**.

All integrations in the tenant now inherit these settings.

## Configure per-integration notification settings

This procedure is optional. Use it when a specific integration has a known credential expiry date, needs proactive reminders before expiry, or should route alerts to a different set of recipients than the tenant default.

1. Go to **Settings > Integrations**.
2. Locate the integration and click the pencil icon to open the **Edit Integration** window.
3. Select **Notifications** from the list on the left side of the **Edit Integration** window.
4. To turn notifications on or off for this integration only, use the **Enable Per-Integration** toggle. When enabled, the integration uses global settings unless you configure overrides below. When disabled, the Aisera Platform sends no credential alerts for this integration even if global notifications are enabled.
5. Optional: In **Known Expiry Date**, enter the date when this integration's credentials expire. This drives proactive reminder emails ahead of the expiry date.
6. Optional: Under **Reminder Schedule**, select when to send proactive reminders before the expiry date. Available options are `30`, `14`, and `1` day before expiry. You can select any combination.
7. Optional: Under **Override Recipients**, add email addresses to route this integration's alerts to a different set of recipients than the tenant default. The **Inherit Indicator** shows the current tenant-level recipients that apply when no override is configured. If you add override recipients, the tenant-level list does not apply to this integration.
8. Click **OK**.

The Aisera Platform applies the configured overrides to this integration going forward.