> ## Documentation Index
> Fetch the complete documentation index at: https://docs.curator.interworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# System Notifications 

> Configure automated email notifications for system alerts, issues, and maintenance updates to improve Curator instance management.

To ensure you are able to easily manage your Curator instance without having to check-in all the time, you
can subscribe to emails that generate from Curator's notification system.  These emails will scan Curator's
running list of issues, suggestions and to-do items that will ensure you have more visibility into your
Curator instance making management easier and increasing stability.

**NOTE**: Email configuration on Curator is required to use this email notification system.  If you have not
configured email on your Curator instance, please get in touch with your email administrator and [use these instructions](https://docs.curator.interworks.com/setup/email/email_configuration.md)
to set up email.

## Enabling Email Notifications

1. Login to the backend of your Curator instance (e.g. `https://www.curatorexample.com/backend` ).
2. Navigate to the **Settings** > **Curator** > **Portal Settings** section from the left-hand menu.
3. Click on the "Notifications" tab at the top of the page.
4. Toggle ON the switch labelled "Send Curator Digests"
5. This will display scheduling options.  Choose your weekly/daily/monthly scheduling options, and whiter or
   not you'd like immediate notifications for new alerts.
6. Click the "Save" button.

## Subscribing to and Un-Subscribing from Email Notifications

There are two ways to manage who receives the admin digest. Subscribing a backend user is always done
from their profile (the first method below); un-subscribing can be done either from the user's profile or
directly from the recipients list on the Notifications tab.

### From the Backend Administrator's profile

1. Login to the backend of your Curator instance (e.g. `https://www.curatorexample.com/backend` ).
2. Navigate to the **Settings** > **Curator** > **Backend Administrators** section from the left-hand menu.
3. Click on the User whose settings you would like to change.
4. Check or un-check the "Subscribe to admin digest" checkbox.
5. Click the "Save" button.

   ![Subscribe Image](https://mintcdn.com/interworks/x0r9dMo3GyjABFAR/assets/images/site_administration/admin_email_notification/admin_digest_subscribe_screenshot.png?fit=max\&auto=format\&n=x0r9dMo3GyjABFAR\&q=85\&s=fab8be424374e8d21c3e5ecb3214cb4f)

### From the recipients list on the Notifications tab

1. Login to the backend of your Curator instance (e.g. `https://www.curatorexample.com/backend` ).
2. Navigate to the **Settings** > **Curator** > **Portal Settings** section from the left-hand menu.
3. Click on the "Notifications" tab at the top of the page.
4. Under **Backend Admin Recipients** you will see one row for each backend user currently subscribed to
   the admin digest. Click the **X** on a row to un-subscribe that user, then click the "Save" button.

**NOTE**: This list mirrors the "Subscribe to admin digest" setting on each backend user, so removing a
row un-checks that user's checkbox. Adding a recipient is only done from the Backend Administrator's
profile (the first method above). At least one administrator must remain subscribed -- if you try to remove
the last subscribed admin, the save is rejected with a validation error, so subscribe another admin first.

### Recipients without a backend account

Digests can also go to people who do not have a backend account.  Add their address to the "Additional
Non-Curator-Admin Emails" field on the "Notifications" tab of **Settings** > **Curator** > **Portal Settings**.  Click
the "Save" button when you are done.

## Tableau Server SSL Certificate Notifications

Users' browsers load embedded Tableau Dashboards directly from Tableau Server, and refuse to do so when the server's
SSL certificate is not valid.  Curator's own connection to Tableau does not verify the certificate, so it checks the
certificate separately, the way a browser would, for each Tableau Server connection that uses an `https://` URL.  When
the connection has an Alternate Tableau Server URL, Curator checks that URL, because it is the one browsers use.  The
result is rechecked at most once an hour.

Each notification names the Tableau connection and links to it.

| Certificate problem | Priority | Shown in the Curator Digest as |
| - | - | - |
| Expired | High | Serious Issues |
| Does not match the server name in the connection URL | High | Serious Issues |
| Curator could not verify it (for example, self-signed) | Medium | Suggestions |
| Valid, but expires within 30 days | Medium | Suggestions |

High-priority notifications mean embedded Dashboards from that Tableau Server are already failing to load, usually
with the error described in
[Tableau Connection Troubleshooting](https://docs.curator.interworks.com/creating_integrations/tableau_connection/tableau_connection_troubleshooting.md#dashboard-error-tableau-server-could-not-be-reached-from-your-browser).
Ask your Tableau Server administrator to install a valid certificate.  The expiring-soon notification counts down the
days until the certificate expires, so the certificate can be renewed before Dashboards stop loading.

The "could not verify" notification is medium priority because Curator checks the certificate against the certificate
authorities its own server trusts, not the ones your users' computers trust.  A certificate issued by your
organization's internal certificate authority can load fine in users' browsers and still raise this notification.  If
embedded Dashboards load, you can ignore it; if they do not, the certificate is the likely cause (for example, it is
self-signed or is missing its intermediate certificate).

All of these notifications also appear in **Settings** > **Curator** > **Status** and clear on their own, within an
hour, once the Tableau Server presents a valid certificate that is not close to expiring.  No notification is raised
when the Tableau Server cannot be reached at all, because Curator's connection check already reports that.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.