> For the complete documentation index, see [llms.txt](https://docs.udara360.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.udara360.io/core-features/operations/notifications/email-report.md).
# Email Report
The Email Report page comprehensively views all system-generated emails, including daily backups, password reset notifications, and other automated communications. This interface allows administrators to monitor, track, and export email communication logs within the banking system.
### Accessing the Email Report Page
1. Log into the Core Banking Application.
2. Navigate to **Operations** in the left sidebar.
3. Click on **Notifications.**
4. Select **Email Report** from the submenu.
## Page Features and Functions
### Email Report Table Information
The table displays the following columns:
1. S/N: Sequential numbering.
2. DESTINATION EMAIL: Recipient's email address.
3. REFERENCE NUMBER: Unique identifier for each email.
4. SUBJECT: Email subject line/purpose
5. DATE CREATED: Timestamp of email generation.
6. STATUS: Delivery status of the email.
### **Export Reports**
1. Click the "**Export**" button.
2. Select the desired format:
* CSV: For data analysis
* Excel: For formatted reports
---
# 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.udara360.io/core-features/operations/notifications/email-report.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.