Notifications
Lithify keeps two parallel notification surfaces: an in-app bell for users who are signed in, and email — sent through the workspace SMTP transport — for everyone else (or for moments that warrant a real ping). The mailer agent is the programmable extension of all this.
In-app
- The bell in the topbar shows unread count + a dropdown of recent items.
- Each notification is scoped to a user. You only see your own.
- Clicking a notification deep-links to the brief or initiative it refers to.
- Per-user toggles let you silence categories you don't care about.
Email digests
For each notification the platform decides whether to also send an email — typically yes when you're not actively in the app. The mail goes out via the workspace SMTP transport and links back to the relevant brief.
Triggers
| Event | Who gets notified |
|---|---|
| Brief assigned to you | The new assignee |
| Brief you're assigned moves state | The current assignee |
Brief you submitted (when known) moves to review or done | The submitter |
| Initiative state change | The initiative owner |
| Workspace invitation accepted | The inviter |
Custom notifications via the mailer agent
For anything outside the defaults, configure a mailer agent instance and wire a workflow rule to fire it. Examples:
trigger: state_enter · ready condition: type = bug AND priority = critical action: run_agent → mailer (instance: "qa-page")
trigger: state_enter · review condition: brief.submitter_email exists action: run_agent → mailer (instance: "thank-submitter")
Authoring style. Mailer agent prompts produce the best results when you tell the model what tone to take and what NOT to include. e.g. "Reply in plain English. Do not include the brief id. Do not speculate on causes."