Message notifications in Dapple are the emails sent to creators and organisers when activity happens on a submission. Understanding which events trigger a notification — and what to do when notifications aren't arriving — helps you stay in control of your project communications and avoid creators missing important updates.
Which events send a notification email?
Event | Who is notified | Sent automatically? |
Submission received | Creator | Yes — always |
Message sent by organiser | Creator | Yes — immediately |
Bulk message sent by organiser | Each creator in the selection | Yes — immediately |
Stage Automation triggered | Creator | Yes — if set to send to creator email |
New message reply from creator | Organisation inbox | Yes — as a standard in-app message |
Status or stage changed | Creator or Org member | Yes depending on the automation set |
Why am I not receiving notification emails?
If notifications aren't arriving, work through this checklist in order:
Check | What to look for | Fix |
Spam / junk folder | Dapple emails may be filtered automatically | Check spam and mark as not spam — add noreply@dapplehq.com to your contacts |
Email address | Wrong address on the account | Go to Account Settings → Email and confirm the address is correct |
Organisation email | Creator replies go to org email, not Dapple inbox | Check the inbox associated with your organisation email address |
Stage Automation not set up | No automation exists for this stage | Add a Stage Automation in Project Settings → Automations |
Bulk send filtered incorrectly | The submission wasn't included in the send | Check the submission's Messages tab — if blank, it wasn't in the recipient list |
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.
A creator says they haven't received my message — what should I check?
Go to the submission detail view → Messages tab and confirm the message shows as sent with a timestamp.
Ask the creator to check their spam folder for an email from noreply@dapplehq.com.
Confirm the creator's email address is correct — go to the submission detail view and check the Creator contact details.
If the email address is wrong, update it and resend the message.
If the issue persists, ask the creator to add noreply@dapplehq.com to their contacts and resend.
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