Notifications
ARDS sends emails when something needs your attention or when something finished. Everything you see in email is also visible in the dashboard.
Email events you might see
- Welcome / activation — once, when your tenant is provisioned. Sender:
update@etiakorp.com. Subject mentions account activation. - Mission decomposed — when a mission's plan is ready and waiting for your approval. Subject names the mission and the task count. The link goes straight to the approval screen.
- Mission completed — when every task in a mission succeeded.
- Mission failed — when a mission can't continue. The email summarises which task failed and why; the link goes to the failing task.
- Attention request — when a coder needs human input mid-task (a clarification, an approval, a decision). The email contains the question text. Use the dashboard link to respond; replying to the email itself doesn't work in v1.
- Task failure — when an individual task errors out (separate from full mission failure, e.g. one task in a five-task mission).
What you won't get emailed about
- Routine task progress (those land in the dashboard only).
- Cost milestones (visible in the Costs dashboard).
- Successful Review Engine findings (they queue up in the Reviews page).
- System maintenance windows — those go via operator-side comms, not in-app email.
Sender domain and spam
All system mail comes from update@etiakorp.com. If you're using Outlook, Live, or Gmail, the first email frequently lands in spam — mark the sender as legitimate the first time and subsequent mail reaches your inbox normally.
We don't send marketing email. If we ever need to send platform-level news, it'll come through the same channel with a clear subject prefix.
Threading
Emails about the same mission are threaded together by mission ID. If you have email-thread view in your client, every notification for a mission lives in one conversation.
Replying to notifications
Replying to a system email lands in our inbound queue but doesn't drive action in the product. For a support reply, use support@etiakorp.com directly. To answer an attention request, click through to the dashboard.
Muting
There's no self-serve mute panel yet — the Settings dashboard holds the platform's configuration values and an audit log, not notification preferences. Recipients and per-event templates are managed on the platform side. If a class of email bothers you, write to support@etiakorp.com and we'll adjust it for you.