> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/administration/settings-center/emails-and-alerts.md).

# Emails & Alerts

Configure We360.ai email notifications, scheduled reports, and workforce analytics alert triggers for employee monitoring.

Use this section to manage notifications, report emails, and alert conditions.

## Email Alerts

Daily reports are delivered promptly at the beginning of each day, while weekly\
reports are sent on the first day of the week, aligning with your chosen timezone.

{% hint style="info" %}
Timezone can be set by using the Set Timezone drop-down menu
{% endhint %}

<figure><img src="https://1096369946-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiXtwQ1TAvSOYwcPeXCN%2Fuploads%2Fgit-blob-43c8c04543bccff28dbe3ae4c29180c2894129f4%2Fsettings-alerts-email-report-timezone-dropdown.png?alt=media" alt="Set Timezone drop-down in Email Reports listing System default and world timezones for scheduling report delivery"><figcaption></figcaption></figure>

Email reports can be used to send:

* Attendance
* Activity
* Productivity
* Shift
* Summary

Reports to specified email address at selected frequency (Daily / Weekly / Monthly)

<figure><img src="https://1096369946-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiXtwQ1TAvSOYwcPeXCN%2Fuploads%2Fgit-blob-6d7b434a5d84feeef7b531bf4217ead68f17b395%2Fsettings-alerts-attendance-report-recipients-frequency.png?alt=media" alt="Attendance Report email settings with recipient search, sample download and Daily, Weekly or Monthly frequency checkboxes"><figcaption></figcaption></figure>

## Alert Rules

<figure><img src="https://1096369946-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiXtwQ1TAvSOYwcPeXCN%2Fuploads%2Fgit-blob-27914de2e11a863f6225ee06dd8a455ac7b59923%2Fsettings-alerts-alert-rules-tab-list.png?alt=media" alt="Alert Rules tab listing an existing overtime break rule with type, name, description and the Add Alert Rule button"><figcaption></figcaption></figure>

Alert Rules can be added by pressing on the `+ Add Alert Rule` button which opens up the following:

<figure><img src="https://1096369946-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiXtwQ1TAvSOYwcPeXCN%2Fuploads%2Fgit-blob-65262442441a2fb4469fb828bea8be68ef886dda%2Fsettings-alerts-add-alert-rule-dialog.png?alt=media" alt="Add Alert Rule dialog with fields for rule name, description, alert type, teams and email recipients"><figcaption></figcaption></figure>

Alert Rule Types can be for:

* Application
* URL
* Overtime break
* Inactivity
* Absence

An Alert Rule, once created, can be Cloned, Edited, or Deleted.

For Inactivity Alerts, Inactivity thresholds from 30 min to 240 min can be selected in 30 min increments to initiate an alert.

Individual Alert (one alert per user for each instance of inactivity) or Summary Alerts (a single consolidated alert for all inactive users, checked every 30 minutes) can be selected.

For Absence Alerts as well, Individual or Summary Alerts can be chosen.

## Common Issues

{% hint style="info" %}
To stop receiving email reports, deselect all report frequencies (Daily / Weekly / Monthly)
{% endhint %}

In case of Individual alerts for Inactivity, repeat alerts for the same user are suppressed for 2 hours to prevent notification fatigue.

In case of Summary alerts for Inactivity, users included in a summary alert will not be repeated for the next 2 hours.

Selecting Individual alerts for Absence can trigger multiple notifications for the same user in a single day. It is suggested to select Summary alert to get a single, consolidated alert per user per day, combining all events into one notification to reduce noise.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.we360.ai/administration/settings-center/emails-and-alerts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
