Build the admin notification configuration UI #39

New issue

Open

opened 2026-07-28 04:57:34 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-07-28 04:57:34 +00:00

Context

v0.3.0 delivers notifications with per-user preferences. Deployment-level configuration â€”
which channels exist and how they are configured â€” belongs to the admin.

Scope

Admin configuration of notification channels and delivery settings.

Implementation notes

Configure available channels and their settings at the deployment level.
A test-send action per channel. Discovering that email was misconfigured at the moment a
real notification was needed is the failure mode worth designing against.
Delivery history with failures, so silent non-delivery is visible.
Deployment-level defaults for event types, which users can then override.
Secrets such as SMTP credentials must be stored and surfaced safely â€” write-only fields
in the UI, never echoed back, and never committed to the repo.
Respect per-user preferences; admin defaults set the baseline, they do not override an
individual's explicit choice.

Done when

Channels are configurable with a working test-send
Delivery history and failures are visible
Deployment defaults exist without overriding explicit user preferences
Credentials are never echoed back or logged

References

docs/circa-spec.md section 11

Depends on: #27 (notifications).

## Context v0.3.0 delivers notifications with per-user preferences. Deployment-level configuration â€” which channels exist and how they are configured â€” belongs to the admin. ## Scope Admin configuration of notification channels and delivery settings. ## Implementation notes - Configure available channels and their settings at the deployment level. - A test-send action per channel. Discovering that email was misconfigured at the moment a real notification was needed is the failure mode worth designing against. - Delivery history with failures, so silent non-delivery is visible. - Deployment-level defaults for event types, which users can then override. - Secrets such as SMTP credentials must be stored and surfaced safely â€” write-only fields in the UI, never echoed back, and never committed to the repo. - Respect per-user preferences; admin defaults set the baseline, they do not override an individual's explicit choice. ## Done when - [ ] Channels are configurable with a working test-send - [ ] Delivery history and failures are visible - [ ] Deployment defaults exist without overriding explicit user preferences - [ ] Credentials are never echoed back or logged ## References - `docs/circa-spec.md` section 11 Depends on: #27 (notifications).

claude-bot added this to the v0.5.0 milestone

2026-07-28 04:57:34 +00:00

claude-bot added the

backend

frontend

labels

2026-07-28 04:57:34 +00:00