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

# User Alerts

User Alerts notify you about important account events related to Couchdrop users.

## Overview

User Alerts send notifications about user account activity across your Couchdrop account.

These alerts are **global**, which means they are configured at the account level rather than for an individual folder, user, or workflow.

Navigate to **Admin Mode > Alerting** to configure User Alerts.

{% hint style="warning" %}

### User Alerts apply across the Couchdrop account.

Use User Alerts when you want account-level visibility into user login activity or account expiry events.
{% endhint %}

## Supported user alerting events

Couchdrop supports alerts for the following user events:

### Login alerts

Couchdrop can send a webhook notification when a user logs in.

Enable **Send notification on Login** under **Webhooks**, then enter the destination endpoint in **Recipient Webhook URI**.

Couchdrop expects the webhook endpoint to return an HTTP `200` response. If it does not, Couchdrop retries the webhook up to 15 times using exponential backoff.

{% hint style="info" %}
Login alerts are available through webhooks rather than email.
{% endhint %}

### User account expiry alerts

Couchdrop can send an email notification when a user account expires.

Under **User Account Expiry**:

1. Enable **Send email on user expiry**.
2. Enter the address that should receive the notification in **Recipient Email Address**.
3. Save your changes.

This notification is independent of login alerts and can be configured separately.


---

# 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.couchdrop.io/administration/alerts-and-notifications/user-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.