> For the complete documentation index, see [llms.txt](https://docs.copia.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.copia.io/docs/devicelink/administration/notifications.md).
# Notifications
## Overview
DeviceLink offers two types of email notifications: **job status notifications** and **critical device backup coverage notifications**.
Job status notifications will send email notifications when it detects a modified Project and/or when a job run fails. These notifications can be sent immediately or in the form of daily or weekly summaries. Immediate notifications include the Site, Project name, Devices, Job name, completion timestamp, and commit message. Summary reports will include counts of job statuses over the selected time period.
Critical device backup coverage notifications are designed to proactively inform users if any critical devices in their organization are not configured properly for backup. If any devices equal to or above the selected device criticality level are not configured for a scheduled backup (for example, because they are manually excluded from the [sitewide backup schedule](/docs/devicelink/sitesandagents/sites/site-settings.md#sitewide-backup-schedule) or they do not have an assigned Agent), this feature will automatically send a report containing a list of the critical devices not backing up.
DeviceLink notifications for Copia users are managed at the user level, so every user may personalize their own notifications. In addition, each site can be configured to send notifications to additional target email addresses not configured as Copia users (e.g. an internal distribution list).
## Managing Email Addresses
To access your notification preferences, use your profile setting. Click the caret next to your avatar in the top navigation bar and choose the *Settings* option.
Choose the *Notifications* section and take note of the *General* container. By default, the email you used during registration will be set as the primary address to deliver notifications.
{% hint style="info" %}
If you wish to send notifications to multiple email accounts, you can add additional email addresses within the *Add Email Address* field. Notifications will be sent to all email accounts that are registered within the *General* container.
{% endhint %}
## Managing User Preferences for DeviceLink
Notifications preferences are managed separately between Copia products. In this section, we will review how to setup e-mail notifications for DeviceLink. These notifications may be individual notifications, or contain summary reports over a defined period of time.
{% hint style="info" %}
Additional reports summarizing Job results can also be found directly, using [Site graphs](/docs/devicelink/sitesandagents/sites/organization-dashboard.md).
{% endhint %}
### Enabling Job Status Notifications
To activate job status notifications for DeviceLink, navigate to the ["Notifications" page](https://app.copia.io/user/settings/notifications) in the user settings. Find the toggle labeled "Enable Job Status Notifications" and toggle it on.
When you enable notifications for DeviceLink, you will receive notifications for Projects you've elected to "watch."
{% hint style="info" %}
To learn more about how to watch or unwatch a Project, check out the [Watching Projects](https://docs.copia.io/docs/devicelink/projects-and-devices#watching-projects) section.
{% endhint %}
#### "Some backups did not start" Notifications
[Sitewide job schedules](/docs/devicelink/sitesandagents/sites/site-settings.md#sitewide-backup-schedule) allow you to back up all projects in a site with a single schedule configuration. As described in the sitewide schedule section:
> If the agent is unable to complete the backups before a new set of backup operations is scheduled (*e.g. because there were too many, or the agent went offline*), the site admins will receive an email letting them know. If the agent was online and running the whole time, this may mean you need additional agent capacity.
{% hint style="warning" %}
This "Some backups did not start" notification is **only** sent to users with DeviceLink notifications enabled.
{% endhint %}
#### Notify Immediately
When this option is selected, Site activity that you set as important will be pushed as individual emails. You can choose to be notified for failed job runs, modified job runs, or both.
{% hint style="info" %}
If your organization has set up [Copia Copilot commit descriptions](/docs/copilot-for-devicelink.md), you can receive Copia DeviceLink commit descriptions in these email notifications.
{% endhint %}
#### **Notify with Report at the End of Each Day**
When this option is selected, a summary report will be emailed each day at midnight in your Site's time zone.
The email will provide a daily tally of Job results, organized by runs that were up to date, modified, or failed/timed out.
#### **Notify with Report at the End of Each Week**
When this option is selected, a summary report will be emailed each Sunday at midnight in your Site's time zone.
This email will provide a weekly tally of Job results, organized by runs that were up to date, modified, or failed/timed out.
Once you're finished with your selections, click the *Save Changes* button.
#### Manually Generate a Report
In addition to scheduled reports, customers can manually generate a report for the sites that they are a member. In the Send Job Run Report Now section, select the start and end dates, and press Send Job Run Report. You will receive a summary email for each of your sites.
### Enabling critical device backup coverage notifications
Critical device backup coverage notifications will send a scheduled report (daily or weekly) of any Devices at or above the chosen criticality level that are not currently being backed up by Copia.
Reasons why a device may not be backing up include, but are not limited to:
* The Device is not associated to a Project
* The associated Project is not associated with an Agent
* The associated Agent is not online
* The associated Project is not linked to a job
* The job linked to the associated Project does not have a schedule
* The associated Project is located in a Site with a configured [sitewide backup schedule](/docs/devicelink/sitesandagents/sites/site-settings.md#sitewide-backup-schedule), but the Project has been manually excluded from the sitewide schedule.
The device criticality threshold for this notification is configurable using the slider.
## Managing Sitewide Notification Targets
In addition to personalized notifications, Copia DeviceLink can also be configured to send email notifications to target email addresses not associated with a Copia user. This can be useful, for example, if you need to send Copia notifications to a distribution list.
These **notification targets** can be configured in the [Organization Settings](/docs/git-based-source-control/administration/org-settings.md). Under the "Email Notifications" tab, you can add an email as a notification target, select the type of notifications it should receive, and choose which Sites the notifications should be sent for.
Notification targets can be edited and deleted after they are created.
In order to prevent conflicts with personalized notifications, notification targets can only be set on email addresses that are not currently associated with a Copia user in your Organization.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.copia.io/docs/devicelink/administration/notifications.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.