Report an Issue

Every screen carries a Report an issue button in the bottom-right. It emails your deployment's support inbox with the reporter's account email and the originating page, so a triager can reproduce with context. The reporter's address is set as Reply-To for a direct thread.

Routing and Transport

Set a recipient and a mail transport in the environment. The transport is chosen explicitly with MAIL_TRANSPORT:

# Recipient inbox (required to enable issue reports)
REPORT_ISSUE_EMAIL=support@yourcompany.com
MAIL_FROM="Your Company <noreply@yourcompany.com>"

# Option A, SMTP (portable, any provider)
MAIL_TRANSPORT=smtp
SMTP_HOST=smtp.yourprovider.com
SMTP_PORT=587
SMTP_SECURE=false
SMTP_USER=apikey
SMTP_PASS=...

# Option B, Amazon SES (host IAM role, no stored SMTP secret)
MAIL_TRANSPORT=ses
SES_REGION=us-east-1   # MAIL_FROM must be a verified SES identity here

With no recipient or transport configured, the button reports that issue reporting is not set up rather than silently dropping the message — fail-loud, not fail-silent. A recipient without a transport, or a transport missing one of its settings, stops the server at startup with the variable named. If reports are not arriving, verify the transport credentials and, for SES, that MAIL_FROM is a verified identity in SES_REGION.