Configure Fibery Notifications
Use Settings → Notifications for event/channel preferences and the Inbox settings icon for delivery controls. Test with another collaborator because your own changes do not notify you.
Before you start: Have access to a sample entity and a colleague who can mention you. Browser notifications also require browser-level permission.
Worked example: A PM wants review mentions in email but routine activity only in the Inbox. A teammate’s mention on a sample Feature should demonstrate the intended delivery path.
Step-by-step guide
Pick the event and channel
Open Settings → Notifications. Decide which events deserve Inbox, email or Slack delivery instead of enabling every channel for everything.
Enable the delivery mechanism
From the notifications settings icon, enable Email, or use Connect for Slack. Confirm the connected account is yours.
Check browser permission
Enable Browser if needed, accept the browser Allow prompt, and use Send test notification.
Use a realistic trigger
Ask a colleague to @mention you on the sample Feature. Check both its source context and the selected channel.
Organize the Inbox
Use Later for deferred attention and Done for processed notifications. Completing a notification is separate from completing the Feature.
Common mistakes
Testing by editing your own record
Notifications are not sent to the person who made the change. Use another collaborator to exercise the path.
Deleting to clear the queue
Deletion is permanent. Done is the appropriate archive-like state when you may need to revisit the notification.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.