Who gets notified when a note is created?
Everyone in the project eligible for notifications learns that a new note has arrived. If the note is already assigned to someone, that person receives the notification specifically.
Notifications
New feedback? Your team knows immediately, without checking a board.
In short
As soon as a new note arrives or a status changes, nootiz notifies the people involved. Nobody has to poll a board or ask daily whether something moved – the information reaches the right person on its own.
- Alert on new notes
- Alert on status changes
- Everyone stays in sync
- No daily check-in questions
Speed comes from short loops
Projects do not get faster because individual tasks get faster – they get faster when the waiting time between tasks disappears. That is exactly what notifications remove: the gap between “feedback arrives” and “someone reacts”.
Who gets notified when a status changes?
When a note moves from “open” to “in progress” or “resolved”, the relevant people are informed – for example the client who originally created the note, as soon as their request has been handled.
Can I turn notifications on or off?
Yes, notifications can be configured per account, so each person decides for themselves what they want to be informed about instead of hearing about every small change in the project.
How do notifications connect to assignment?
An assignment without a notification would be pointless, because nobody would learn in time that a task is theirs. The two features work together: assignment defines who is responsible, notification makes sure that person actually finds out.
How often do notifications fire when a lot of feedback comes in?
Notifications follow actual events like new notes or status changes, not a fixed schedule. During an intense feedback round there are more of them, during a quiet week there are fewer.
What mistake commonly happens without notifications?
Without active notifications, teams check the project only sporadically and miss urgent feedback for days. That costs real response time, especially on client projects with a tight timeline.
What are the limits of the notification feature?
Notifications inform you about events inside nootiz. They do not replace general project communication about strategic decisions – a conversation or a separate message outside the tool is still worthwhile for that.
What happens with several client projects running at once?
If you run an agency or freelance practice maintaining several websites in parallel, notifications stay tied to their project: a new note on client A's website shows up as an alert for that project specifically, not mixed in with client B's status. That keeps your inbox or notification overview manageable even with ten or more active projects running side by side, without anyone having to manually jump between separate project lists. Anyone only actively involved in certain projects only sees events from the projects they are part of anyway, which narrows the view further instead of cluttering it with irrelevant updates from someone else's client work.
Frequently asked questions
Can I control notifications?
Yes, notifications can be configured per account.
Do I get a notification for every single note?
You are informed about new notes and status changes; the exact configuration is set in your account.
Does the client also receive notifications?
Yes, the client is also informed when the status of their note changes, for example when an item is marked resolved.
What happens if I don't want to receive notifications?
You can disable notifications in your account and check the project manually through the list instead.
Are notifications sent immediately or with a delay?
Notifications are triggered as soon as the relevant event occurs, so immediately on a new note or status change.
Do notifications replace a daily status meeting?
They make many of them unnecessary, because the current state is always visible directly in the note list itself.
Do notifications from several client projects get mixed together?
No, notifications stay project-specific, so every alert shows which client project it belongs to.
Keep reading
Deeper pages on platforms, comparisons and hands-on workflows.
Use case
Website feedback for web designers
Design feedback that is unambiguous: your client marks the element, you get an actionable change instead of a description.
→Use caseBug feedback for developers
For developers who want to fix reports without first asking where the issue happened and on what.
→GuideWebsite feedback tools: categories compared
An overview of tool categories for website feedback, and which questions actually matter when choosing one.
→FeatureNotes directly on the website
Click, type, done – feedback lands exactly where it belongs.
→PlatformWebsite feedback tool for Shopify stores
For Shopify you add the nootiz snippet to your theme's theme.liquid – ideally in a duplicated theme so the live store stays untouched. Using the theme preview link, your team comments directly on product, collection and content pages.
→GuideShortening feedback loops: why projects really stall
Projects rarely slip because work is slow – they slip because of waiting time. Here is how to cut it systematically.
→Stop collecting feedback in email threads
Add the snippet, share the link, collect feedback right on the page – live in under 5 minutes.