Client Alert Recipients

Where an operator configures which email addresses hear about a specific client's connection-health problems, stalled file-server agents, and 24-hour advance warnings. See the Notifications & Alerts overview for what each of these emails actually contains and when it fires.

Where this lives

In the dashboard, go to Settings → Client Alert Recipients. This is its own tab, separate from every other tab on the Settings page.

Every other tab (Account, Session Timeout, Notifications, Scheduled Notifications, Activity Log, About) is scoped to the operator’s own account. This is the only tab that operates per tenant.

The tab shows a client picker first: a dropdown listing every tenant on the account. Recipients cannot be managed until a client is selected — there is no general or default configuration shown in the meantime. Each client’s list is independent of every other client’s.

Adding and removing recipients

Once a client is selected, its current recipients appear as a list of removable chips, each showing one email address. To add a recipient, type an address into the text field and either press Enter or click the add button next to it. To remove one, click the small remove control on that recipient’s chip.

Note
Each add or remove is its own request. There is no separate save step and no draft state to discard.

A client with nobody configured shows an explicit empty state rather than a blank list, so it is clear no recipients have been added yet rather than the page having failed to load them.

An empty recipient list is valid, not an error
A tenant with no recipients configured simply does not receive these emails — nothing fails or halts because of it. Connection-health, stale-agent, and 24-hour advance-notice alerts all check whether the tenant has any recipients before sending, and silently skip sending for that tenant if the list is empty.

Validation and duplicates

Each entry submitted must be a syntactically valid email address; the request is rejected if it is not. Attempting to add an address already on the list has no effect — a client’s list cannot contain the same address twice. There is no fixed limit on how many recipients a single client can have.

Who can see and change this list

This tab is reachable by any operator who can sign in to the account and open Settings — there is no separate role restriction specific to this tab.

Every add or removal is recorded to the account’s activity log, identifying which operator made the change and for which tenant.

Distinct from two other recipient lists
This list only ever receives the three alert types described on the Notifications & Alerts overview. It is not the same list as the operator’s own account-level notification settings, and it is not the same list as the self-service portal’s own recipient list for restore-request lifecycle events, which is configured separately on the Self-Service tab.