Email Notifications: Controlling What Your Workspace Sends

Email notifications are how people find out something happened without keeping Atarim open. Two things decide whether a message lands: what your workspace has switched on, and what each person has set for themselves. There's also a batching window in between, which is why notifications arrive in groups rather than one per click. This article covers all three, plus the activity that never generates email no matter what you set.

Step-by-Step Guide

Where to Find It

1. From the main dashboard, select Settings.
2. Under Communication, select Notifications.

The panel is headed Email Notifications and holds two sections: Additional recipients at the top, and Notification types below the divider.

If your workspace hasn’t finished Inbox Setup, selecting Notifications opens the four-step email wizard instead of this page. That’s expected — use Back to Email Settings beneath it to skip out, or complete the wizard first.

What Triggers an Email

Five kinds of activity can generate a notification email:

• A new task is created
• A new general task is created
• A comment is added
• A task’s status changes
• A file is uploaded to a task

Due date reminders are sent separately and don’t follow these rules — see below.

Anything else passes silently. The three that catch people out most often:

• Changing a task’s priority sends nothing. Priority is not one of the activities that generates email, so raising something to urgent won’t alert anyone on its own. Change the status or leave a comment if you need people to know.
• Being mentioned in a comment sends nothing. Mention-based notifications don’t exist in Atarim. If you’re on a task and someone comments, you’ll be notified because of the comment, not because you were named in it.
• Being assigned to a task sends nothing. Assignment doesn’t email anyone. It puts them in scope for that task’s future activity.

How Notifications Are Grouped

Atarim doesn’t send an email the moment something happens. Instead it opens a 15-minute window:

1. Activity happens on a project. A 15-minute timer starts.
2. If more activity happens on that same project before the timer runs out, it’s added to the group and the timer restarts.
3. Once 15 minutes pass with no further activity, one email goes out covering everything in the window.

So a burst of ten comments produces one email, not ten. It also means notifications are never instant — the fastest anything arrives is roughly 15 minutes after the last thing happened.

Grouping is per project, not per task or per person. Activity on different tasks within the same project shares one window and arrives in the same email. Activity on a different project is grouped separately.

The Six Notification Types

Under Notification types you’ll find six switches. All six are on by default for a new workspace.

The page describes these as applying for all users on the workspace.

Turning Notifications On and Off

1. Select the switch beside any notification type.
2. The change is stored immediately — there is no Save button on this page.

Saving is deferred very briefly, so flipping several switches in a row is sent as one update rather than one request per switch. Leaving the panel, switching tabs, or clicking out of the recipients field flushes anything still pending.

In practice that means you can toggle what you need and navigate away without losing anything. But it also means there’s no confirmation step and no undo — switching something off takes effect for the whole workspace straight away.

Additional Recipients

The Additional recipients field sends a copy of every notification to addresses that aren’t workspace users — a shared support inbox, a project manager, an archive address.

1. Select the Additional recipients field.
2. Enter one or more email addresses, separated by commas.
3. Click outside the field. The change saves on its own.

These addresses receive a copy on top of your workspace users. Adding one doesn’t replace anyone or reduce what your team gets.

This field is plan-gated. If your plan doesn’t include it, the label carries an upgrade badge naming the minimum plan, and selecting the area opens an upgrade prompt rather than letting you type.

Who Actually Receives Them

Three conditions all have to be met before a given person gets an email.

1. They’re on the project

Only people with access to a project can be notified about activity in it.

2. They’re on the task

Notifications go to the people attached to that specific task. Being on the project isn’t enough — if you aren’t on the task, activity there won’t reach you.

Assigning someone to a task doesn’t email them. What it does is put them in scope, so they start receiving the comment, status and task notifications for it.

Administrators can control whether someone is added automatically. Open People, select the member, and under Add to new projects and tasks by default you’ll find two switches:

• Add to new projects by default — the member is added to every new project as it’s created.
• Add to tasks by default — the member is added to new tasks automatically.

Both are admin-only, and both are upstream of everything else here. Someone who isn’t being added to tasks won’t be notified about them no matter what the notification switches say.

3. Their own preferences allow it

Further down the same screen, under Assigned Tasks Notifications, each person has three switches:

• Every new task
• Every new comment
• Every status change

Administrators can change these for any member. Everyone else can only change their own. New members joining a workspace start with all three switched on.

Due Date Reminders

Due date reminders are a separate email from everything else on this page. They go to whoever the task is assigned to, and they aren’t controlled by the workspace switches or by anyone’s personal preferences.

A reminder is sent at five points around a task’s due date:

• Two days before it’s due
• One day before it’s due
• On the due date
• One day overdue
• Seven days overdue

Each person gets one email covering all their tasks at that point, grouped by due date, with the task title, the project, its current status, and who set the due date.

Two conditions have to be met. The task must have someone assigned — an unassigned task with a due date reminds nobody. And the task must not be complete; completing it stops the reminders.

What Never Sends an Email

Some activity produces no email regardless of your settings:

• Internal tasks. Anything marked internal is excluded entirely — by design, since internal tasks are for your team rather than the client.
• Priority changes. Not a notifiable activity.
• Mentions in comments. Not supported.
• Being assigned to a task. Assignment itself sends nothing.
• Design uploads. Adding a design is excluded from notification email, unlike a file attached to a task.
• People with no notification preferences set. Someone with no preferences recorded receives nothing rather than everything.

FAQs

Conclusion

Automating notifications in Atarim ensures that your team and clients stay informed without the need for constant manual updates. By setting up custom notification triggers and choosing the right recipients, you can keep your projects on track, ensure timely responses, and avoid bottlenecks. Start using automated notifications today to improve communication and workflow efficiency.