Notification Types
Which events notify you in Elixion, who receives them, where they land, and how to change that
Notification Types
Notifications in Elixion, the platform for Engineering Intelligence™, are per person. They land in your Inbox and, depending on your settings, in your email.
Events that notify you
These are the events raised by day-to-day work on an issue.
| Event | Who is notified |
|-------|-----------------|
| Issue assigned | The new assignee, unless they assigned it to themselves |
| Comment on an issue | The issue's assignee and reporter, minus whoever wrote the comment |
| Issue status changed | The issue's assignee and reporter, minus whoever changed it |
| Mention | The person named with @ in a comment |
Someone who is mentioned in a comment receives one notification, the mention,
even when they are also the assignee or the reporter. Mentions come from the
people the editor actually recorded, not from a scan of the comment text, so
typing an @ in prose does not notify anyone. The excerpt shown in the Inbox
and the email is the first 150 characters of the comment as plain text.
Other events reach you outside the issue flow:
- A Jira or Linear import finishing or failing.
- A pull request being auto-merged, or failing to auto-merge.
- Wallet alerts, if your workspace uses a prepaid wallet: low balance, a failed auto-refill, or a run blocked for funds.
- System announcements from the platform.
Each notification carries a priority: low, medium, high or urgent.
Where they land
The Inbox
The bell in the top bar carries your unread count and opens your Inbox. The
same list is at /inbox.
- The header reads how many things need you, or that you are caught up, with counts for Unread, Urgent and Total.
- Four filters: All, Unread, @you for mentions only, and Agents for anything an agent did.
- Mark all read clears the unread state in one go.
- Opening an item offers Archive.
- Each row links straight to what it is about: the issue by its key, or the sprint, project or agent involved.
New notifications arrive without a page reload.
Email is sent for the events above unless you have turned the email channel off. Issue activity, meaning assignment, comments, status and priority changes, and mentions, is sent as it happens rather than held for a digest.
Each of those event types has its own email template.
Channels
Elixion delivers notifications in the app and by email. Those are the two channels the settings page offers, and the two the product sends.
Slack is not a notification channel. The Slack integration reacts to webhook events; notifications are not routed to it. A project's Slack channel field is a label on the project, not a delivery target.
Changing what reaches you
Open Settings > Notifications. Every switch saves immediately.
Channels
- Email notifications: receive notifications by email.
- In-app notifications: deliver notifications live inside Elixion.
Turning the in-app channel off stops the live delivery. The notification is still recorded and still listed in your Inbox.
What you are notified about
A list of eight events: issue assigned to me, comments on my issues, mentions, issue status changes, sprint started, sprint completed, deadline reminders, and document shared with me.
These preferences are recorded against your account. They do not currently change what is created or what is delivered. The channel switches and the quiet hours below are what govern delivery.
Quiet hours
Set a From and a To time. Both ends are needed: a half-filled pair is not saved, and Clear turns quiet hours off.
During quiet hours nothing is delivered except urgent notifications. The notification is still created and still appears in your Inbox, and there is no catch-up send when the window ends.
Quiet hours are read in UTC.
Custom rules
A second card lets you save a rule with a name, a description, an event, a priority, its channels and an active switch. Rules are stored and listed here. What is delivered today is decided by the channel switches and quiet hours above.
Through the Claude connector
The connector can list your unread notifications and mark them read, scoped to the workspace the connection was granted. Notifications outside that workspace are reported back as out of scope rather than touched.
See Claude connector.