Managing notifications
Which channel carries what, which alerts you should not switch off, and how to stop the rest.
EveryoneUpdated 2026-07-30
Notifications on a marketplace are not noise — several of them are attached to a deadline. A missed submission notice can auto-release a milestone; a missed requirements request can stall a project you are paying for. So tune them, but tune them knowing which ones cost money.
| Channel | What it is for | Reaches you when |
|---|---|---|
| In-app (bell) | The full history of everything | You are using the app |
| Important project and payment events | You are away — the reliable fallback | |
| Mobile push | Time-sensitive events | You have the app installed and allowed it |
The ones with a clock attached
- A milestone submitted for your review — the review window is running from that moment, and silence releases the money.
- A revision request or a dispute — both need a response to move.
- A requirements request from your expert — the grace period is running.
- Identity verification expiring — experts get warned 30 days ahead; ignoring it stops expert actions.
- A payout problem — usually a detail the processor needs from you.
You can turn most notifications off, and the underlying deadlines keep running regardless. If you mute project email, put the review window in your own calendar instead.
Practical tips
- Adjust everything in Notification settings; the same preferences apply to web and mobile.
- Unread counts on Messages and the bell are live, so a cleared badge means genuinely read, not merely opened.
- On mobile, push also needs the operating system’s permission — if you denied it at install, the app setting alone will not help.
- Verify your email address. An unverified address is the most common reason someone "never got told".
notificationspreferencespushemailunread
34 articles · Ask a question