Overview
Notifications help you notice work that needs attention, such as mentions, assignments, comments, approvals, status changes, or workflow updates. The notification inbox gives you a central place to review those updates and return to the related records.
Use this article to understand the inbox, unread and read handling, personal notification preferences, module-specific settings, and practical ways to reduce noise.
Who can do this
- Everyone: Everyone manages their own notification preferences.
- Personal accounts: Everyone in the space can do this, including Limited Members.
Open and review notifications
- Open
/notifications. - Start with unread notifications so you can focus on new activity.
- Open a notification to view the related record when a link is available.
- Handle the action, such as replying, reviewing, approving, updating a task, or confirming the change.
- Mark the notification as read when it no longer needs attention.
Unread vs read
| Status | Meaning | How to use it |
|---|---|---|
| Unread | You have not reviewed the notification yet, or you intentionally left it as a reminder. | Use unread as your short-term action queue. |
| Read | You reviewed the update or no longer need it in the active queue. | Mark notifications read after the work is handled. |
Tip: Treat unread notifications like a working inbox. If everything stays unread, the list becomes less useful for urgent work.
Adjust personal notification preferences
Open Account settings > Notifications from the user menu to adjust notifications for your own account. These preferences affect your experience without changing what other teammates receive.
- Turn on notifications for assignments, mentions, approvals, and updates that require timely response.
- Turn off categories that do not help you act.
- Review delivery channels if your workspace supports multiple destinations.
- Update preferences after your role changes or after you join a new workflow.
Review module-specific settings
Some workflows may also have module-level notification behavior. For example, time approvals, finance review, project changes, or team resource workflows may have settings that affect who is notified and when.
| Workflow | What to check | Who should review it |
|---|---|---|
| Task assignments | Assignment and mention notifications. | Team leads and daily users. |
| Approvals | Approval request and approval result notifications. | Managers, finance users, and approvers. |
| Billing or finance | Invoice, contract, budget, or payment-related updates. | Finance leads and admins. |
| Integrations | External channel behavior, such as chat or email alerts. | Admins and integration owners. |
Reduce notification noise
- Keep action alerts on: Assignments, mentions, approvals, and direct requests are usually worth keeping.
- Trim passive updates: Turn off updates that are informative but rarely change what you do.
- Use comments intentionally: Mention people only when they need to respond.
- Review after launch: Notification needs often change after the first week of real work.
Troubleshooting
| Problem | What to check |
|---|---|
| You are missing notifications. | Check personal preferences, module settings, and whether you have access to the related record. |
| You receive too many notifications. | Turn off low-value categories and ask teams to use mentions only when action is needed. |
| A notification opens a page you cannot access. | Ask an admin to review your permissions for the related module or record. |
Next steps
Review your notification preferences after your first week, after joining a new project, and any time unread notifications stop feeling actionable.