Keep your team in sync

Team notification emails from the events that matter

Comment added, task assigned, file shared, team member invited — each collaboration event triggers the right notification email to the right people.

Why team notification emails are often inconsistent

Notification logic scattered across features

Comment notifications, task assignments and team invites are built separately by different teams, each with their own email logic.

No central visibility into what was sent

When a user says "I never received the comment notification", there is no single place to check delivery status.

Localisation skipped for notifications

Notification emails are often only in one language, even when the product supports multiple locales.

Template updates require code changes

Tweaking the copy for a task-assigned notification means a code change, review, and deployment.

One event per collaboration action — one consistent notification

Route all collaboration events through else.events

comment.added, task.assigned, file.shared — each fires an event. Rules and templates handle the right email per event type.

Role-aware notifications

Include the recipient's role in the payload. Rules can route differently for admins vs members — or suppress certain notifications for free-tier users.

Locale-aware from the payload

Include the recipient's locale. The right language template is selected automatically.

Central delivery log

Every team notification logged with event type, recipient and delivery status. Support questions answered in seconds.

Team notification events

comment.added

Comment added

Notify mentioned users or thread participants when a comment is posted.

task.assigned

Task assigned

Notify the assignee when a task or ticket is assigned to them.

team.invited

Team member invited

Send the workspace invitation to the new team member.

team.role_changed

Role changed

Notify a user when their permissions or role in a workspace change.

workspace.activity_digest

Workspace activity summary

Digest of recent workspace events for inactive members.

Frequently asked questions

Can I suppress certain notifications for free-tier users?
Yes. Include the user's plan in the event payload. Rules can be set to match only on certain plan values, suppressing the notification for others.
Can team notifications be sent in the recipient's language?
Yes. Include the recipient's locale in the event payload. Rules route to the localised template automatically.
How do I handle notification preferences (e.g. a user who turned off comment emails)?
Your backend should not fire the event for opted-out users. else.events does not manage notification preference state — that lives in your application.
Can I send notifications to multiple recipients from one event?
else.events currently handles one recipient per event send. For multi-recipient notifications, fire one event per recipient or handle fan-out in your backend before firing.

Team notification emails that arrive when they should

One event per collaboration action, consistent template, central log. No custom notification service.

  • Free during public beta
  • Role and locale aware
  • Central delivery log for support