Organization - Section
- Critical Update Management
- Group Management
- Member Management
- Temporary Access Management
- API Key Management
- Activity Browser
- Organization Index Management
- Notification Management
- Privilege Management
- Join an Organization
Adding and Managing Notifications
On the Notifications page, Coveo Cloud organization member can configure notifications to be informed when certain events (activities) occur in their organization. For instance, you could choose to receive an email when a source fails to rebuild. These periodical customized reports allow you to watch closely certain events, errors, or changes in your organization.
Members of the Administrators built-in group can review and delete the default subscriptions and those created by organization members (see User Notifications). As an administrator, you can also subscribe to custom notifications (see Add/Edit an Organization Notification).
The organization notifications you set up on the Notifications page are similar to the user notifications one can configure, but offer additional options (see User Notifications). As an administrator, on the Notifications page, you can configure notifications to be sent via a webhook or JSON email, rather than in a classic email. Moreover, this page displays all organization and user notifications created by your organization users.
Unlike user notifications, organization subscriptions are not deleted when their author is deleted from the organization. They remain active and keep sending reports to the specified webhook or email address. Hence, users wanting to receive notifications for their own use should create a user notification. Temporary users and administrators wanting to receive the notifications as JSON content or as a post to an endpoint should create an organization notification.
By default, the organization contact is notified when a member of their Coveo Cloud organization hits a license limit (see Organization ID and Other Information).
The organization contact receives an email when an organization member opens a dashboard that contains a number of cards exceeding your organization license agreements.
If the default subscription has been deleted, you can recreate it by adding a user notification with the following configuration (see Add/Edit a User Notification). This configuration alerts you whenever an organization limit is hit (see limits in the Settings Panel).
Parameter Value Notification frequency Instantly Results All Resource types Licenses Operations Limit hit
If a notification subscription encounters too many errors, Coveo automatically disables it and sends you a
Coveo Cloud Notification Disabledemail. Errors susceptible to trigger an automatic disabling are typically due to a configuration issue and can usually be fixed by an administrator.
Your organization notification subscription could be deactivated due to one of the following issues:
- Your organization has reached its daily notification limit;
- Your webhook server is unreachable or returns an error;
- Your user identity no longer has the privileges to view the information in the notification.
Once the issue is fixed, click the button in the email to re-enable the notification subscription. Alternatively, you can re-enable it from the Notifications page (see Disable/Enable an Organization Notification).
Add/Edit an Organization Notification
Disable/Enable an Organization Notification
When you want Coveo Cloud to stop sending email notifications without deleting the corresponding notification configuration, you can disable it. To start receiving these notifications again, you can enable them again.
Notifications can also be automatically disabled if they encounter too many errors (see Note: Notification Automatically Disabled). You then receive a
Coveo Cloud Notification Disabled email listing possible solutions. Once you have fixed the issue, you can re-enable notifications to start receiving them again.
On the Notifications page, click the notification to disable/enable, and then in the Action bar, click More > Disable/Enable.
Test an Organization Notification
You can test a notification to ensure that you receive the expected information. For instance, you may want to check that your webhook receives your notifications, or that email notifications are not sent to your spam folder.
On the Notifications page, click the notification to test, and then in the Action bar, click More > Test.
Delete an Organization Notification
On the Notifications page, click the notification to delete, and then in the Action bar, click More > Delete.
Review the Usage Statistics of an Organization Notification
You can review the number of successes, failures, errors, and cancellations related to a notification for troubleshooting purposes.
To review the usage statistics of an organization notification, on the Notification page, click the notification to review, and then in the Action bar, click Usage Statistics.
The Usage Statistics panel displays the following information:
Number of successes: Number of times today that the notification was successfully processed and sent to the expected email addresses or service URLs.
Number of failures: Number of times today that the email or webhook server to which the notification was sent returned an error or could not be reached.
Number of errors: Number of times today that an unexpected error occurred while Coveo Cloud was processing the notification.
Number of cancellations: Number of times today that the activity related to the notification occurred but did not cause a notification to be sent (e.g., the Daily email notifications limit was reached (see Organization Limits).
Review the Activity Regarding Notifications
On the Notifications page, in the right section of the page header, click the Activity icon () (see Review Events Related to Specific Coveo Cloud Administration Console Resources).
If the Activity icon is grayed and unresponsive, you do not have all of the required privileges to perform this action.
The information you can review on the Notifications page table is:
The name of the notification.
The description of the notification.
The format in which you chose to receive the notifications. Available options are Email, Email JSON, and Webhook (see Notification Types).
The identity that created the notification.
The default subscription author is
The frequency at which the author will receive the notifications.
The indicator shown is based on the notification error rate, i.e., the number of notifications that could not be sent due to an error, a failure, or a cancellation divided by the total number of notification attempts since the notification was configured (see Review the Usage Statistics of an Organization Notification). Coveo Cloud considers that a notification cannot be sent when the email bounces back or when a webhook is down, for instance. The indicator is updated every five minutes.
The error rate may be reset if no notification has been sent in a long time. The status then returns to Unknown.
Use this indicator to identify notifications that encounter frequent issues.
The possible values are:
Unknown - Grey indicator
No notification has been sent yet.
Good - Green indicator
Less than 5% of the notifications could not be sent successfully.
Warning - Yellow indicator
Between 5 and 20% of the notifications could not be sent successfully. There may have been occasional issues, or your email or webhook server may have recently been unreachable.
Problematic - Red indicator
More than 20% of the notifications could not be sent successfully. There may have been regular issues, or your email or webhook server may have recently been unreachable.
A webhook notification is successfully sent on the first nine attempts following its creation. The error rate is therefore 0%, i.e., 0 notifications that could not be sent out of 9 delivery attempts. The notification status is Good.
On the tenth attempt, your server is down, and the delivery process fails. The error date is then 10%, i.e., 1 failure out of 10 attempts. The notification status is Warning.
Your server is back up and the notification delivery process is successful again. On the 21st attempt, the notification error rate falls under 5% (1 failure out of 21 attempts), and the notification status changes back to Good.
Last Modified column
The date and time of the last notification modification.
|Action||Service - Domain||Required access level|
Organization - Notifications
Organization - Activities
Organization - Notifications
A member allowed to view activities (i.e., the View access level on the Activities domain) can see activities from administration console pages they do not have the required privileges to access (see Privilege Management and Activities Domain).