Notifications: the Bell and Your Email
What the bell shows, how to turn on email, and which events send one.
The bell counts work handed to you and opens it in one click. A new account sends no email: each person opts in, per event, to one message per item or one a day. Assignment mail always goes out at once.
Qaid tells you about new work in two places: the bell in the dashboard, and email. The bell needs no setup. Email is off until you turn it on.
Read the bell
The bell sits in the top bar of every dashboard page. A red badge counts your unread notices, up to 9+.
Open the list
Click the bell. It shows your ten newest notices, unread ones marked with a dot.
Open a notice
Click one. It is marked read and the feedback it is about opens.
Clear the badge
Mark all read marks every notice read without opening anything.
Every notice is an assignment. It reads “Feedback assigned to you in” and the project’s name, with the visitor’s message under it when there is one. You get one whether the assignment was one item or a batch. Assigning to yourself sends none. The bell checks for new notices every 30 seconds while the tab is open, and again when you come back to the tab.
Choose which emails you get
Open your notification settings
Click Settings in the left rail, then the Notifications tab.
Turn email on
Flip the switch beside Email. A new account starts with it off.
Choose how often
Pick Immediate or Daily Digest. The next section compares them.
Choose the events
Under Events, light up the ones you want: Feedback, Assigned and Escalate. They all start off.
Each click saves at once and shows “Saved”. The settings belong to you and cover every project you are on. There is no project-wide mailing list: each teammate makes their own choice.
Pick immediate or a daily digest
Immediate sends an email for each item as it arrives.
Daily Digest sends one email a day covering the last 24 hours, with a section for each project that had news. A section holds the positive and negative split, the top pages, notable comments, quest responses, and on Pro, AI themes. It also has an Activity block for team changes: someone joined, made an API key, published a quest or connected an integration. You are never told about your own changes. A day with nothing to report sends nothing.
Assignment emails ignore this choice and always go out at once.
What sends an email
Email goes to the project’s creator and its members, each by their own settings. Nobody outside the team gets one.
| Event | You need | Immediate | Daily Digest |
|---|---|---|---|
| New feedback | Email and Feedback | One email per item | In the digest |
| Feedback escalated by a rule (Pro) | Email and Escalate | ”🚨 Escalated feedback on” your project | In the digest, marked escalated |
| Feedback assigned to you, one item | Email and Assigned | ”📌 Assigned to you: feedback on” your project | Sent at once |
| A batch assigned to you | No email; bell only | No email | |
| A quest response | Email and Feedback | ”📋 New response to” the quest | In the digest |
| A teammate’s change to the project | Email and Daily Digest | No email | In the Activity block |
The new-feedback email goes out the moment a visitor clicks a thumb, before they type, so it often shows no message. The digest waits for the message and quotes it.
A rule that matches words in the message runs once the visitor sends it. If you take both Feedback and Escalate, that item sends two emails: the new-feedback one on the click, then the escalation one. An item a rule flags on the click, for example by its page, sends only the escalation email, so someone with just Feedback on gets none for it. Escalation rules need Pro; see Free vs Pro.