Dapple sends notifications for messages on both sides — creators get an email when you message them, and team members get an in-app notification when a creator replies or a teammate @-mentions them. This article covers how the notification system works on both sides.
Notifications for creators
When you (the organisation) send a creator a message, they receive:
An email to the address linked to their Creator Account.
An in-app notification in their Creator Dashboard.
The email contains the body of your message and a 'View message' link that signs them into their account. They can read the full thread, reply (if you allowed replies), and manage other submissions from there.
Emails to creators look like this:
Notifications for team members
When something happens that you need to know about, Dapple sends an in-app notification (the bell icon in the top-right). Triggers include:
A creator replies to a message you sent.
A creator replies to a message thread you're part of (even if you didn't send the original).
A teammate @-mentions you in a Discuss note on a submission.
A submission is assigned to you.
An export you triggered is ready to download.
Click the bell to see your full notification panel.
Can creators turn off email notifications?
Yes. Creators can manage their notification preferences from their Creator Account settings. Options include:
All notifications on — email for every message and stage change.
Only critical notifications — email only for messages from organisations.
All off — no email notifications. They'll only see updates when they sign in.
Most creators leave email notifications on — they want to know when they get a message.
Can team members customise their notifications?
No, at present, you cannot customise the email notifications your receive.
How fast do notifications arrive?
In-app notifications: instant — they appear in the bell icon within a second or two of the action.
Email notifications to creators: usually within 1–2 minutes. Delivery time depends on the creator's email provider.
Email notifications to team members: same — 1–2 minute delivery typical.
Best practice
Encourage creators to whitelist noreply@dapplehq.com so notifications don't end up in spam.
Click 'Read All' in the team notification panel at the end of each working session — keeps your inbox tidy.
If you're sending time-sensitive bulk messages, factor in 2–3 minutes for emails to land before chasing.
Don't rely on notifications alone — use Saved Views and filters for daily work-finding.
Where to go next