> For the complete documentation index, see [llms.txt](https://docs.arthajobboard.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arthajobboard.com/admin/manage-data/view-job-alerts.md). # View Job Alerts A page where an admin can view the Job Alerts set by candidates, filter the job alerts by status as per the customized date range, and also export the Job Alerts. ## **How to manage Job Alerts?** Navigate to **Manage Data ➝ Job Alerts Section,** There will be a a table with all the job alerts. Here's the tutorial video followed by detailed steps: {% embed url="" %} ## **1. Job Alert Table**: * Displays all job alerts along with their associated email addresses. * Email addresses in these tables may appear multiple times, reflecting different job alerts tied to the same email.

* **List of Preferences**: Email, Frequency, Job Type, Categories, Locations.

## **2. Export:**

* **Export Option**: Admins can export the full list of job alerts in **XLSX format**. ## 3. Filter: * **Filter Option**: Filters allow admins to narrow down results by, Date Range & Status. * **Date Range**: Filter by a specific Date range (e.g., last 30 days, last 6 months).

* **Status**: The Status field includes two distinct states: 1. **Active**: If you click on active, it indicates that the job alert is currently subscribed and is actively sending notifications to the user. 2. **Inactive**: If you click Inactive, It indicates that the job alert has been unsubscribed or is not sending notifications.

--- # 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.arthajobboard.com/admin/manage-data/view-job-alerts.md?ask=&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.