Settings & Notifications
Project email notifications
Choosing what the team is emailed about, and keeping notifications useful rather than ignored.
Last updated September 2, 2026
Members and contributors can be emailed when things happen on a project. The settings decide which events are worth an email.
Choose deliberately
A project that emails everyone about everything trains people to filter it, and then the one message that mattered gets filtered too. Notify on the things somebody has to react to, not on every edit.
| Usually worth an email | Usually not |
|---|---|
| Being added to a project or a task. | Somebody editing a note. |
| A task assigned to you. | Routine progress on somebody else's task. |
| A change to scope or a key date. | Every file upload. |
External contributors
Contributors are emailed too, so an outside agency gets whatever you have switched on. Check the settings before adding people from outside the business — notifications carry project detail into their inbox.
NOTIFICATIONS ARE NOT THE PROJECT
They are a prompt. The board and the task list are where the work actually lives, and a team that only reacts to emails will miss everything that did not generate one.