Notifications and Alerts
Review in-app activity and configure organization alert delivery for supported modules.
What this module does
The notification center gathers supported CapitalOS activity into one list. Users can separate all, unread, and read items, filter by module, inspect severity and timing, open the related context, and mark individual items or the full list as read.
Organization alert settings provide an additional layer for operational delivery. Slack configuration can route supported module updates to selected organization channels.
When to use it
Use notifications to catch up on activity that occurred while you were working elsewhere in CapitalOS. Module filters are useful when you only want updates from Products, Research, Quotation, Testing, or Returns.
Use organization alert settings when a team needs repeatable delivery rules or module-specific Slack destinations rather than relying only on each user’s notification list.
How it fits into CapitalOS
Notifications link cross-module events back to the work that produced them. Their usefulness depends on the events supported by each module and the current user’s access.
Alerts and Slack delivery are configured at the organization level, so they complement rather than replace the personal in-app notification center.
Main concepts
- Notification: an in-app record of supported activity.
- Unread state: an item that has not yet been acknowledged by the user.
- Module filter: a way to narrow the list to a supported CapitalOS area.
- Severity: the importance level displayed with a notification.
- Related context: the CapitalOS record or area associated with the event.
- Alert setting: an organization rule controlling supported operational alerts.
- Slack channel mapping: the organization channel selected for a module’s supported messages.
Typical workflow
- Open the notification center and review the unread count.
- Select all, unread, or read items.
- Filter by module when investigating a specific workflow.
- Open a notification to review its related CapitalOS context.
- Mark handled items as read, or mark all as read after completing the review.
- If the team needs external delivery, ask an organization administrator to review alerts and Slack channel mappings.
- Confirm that the target integration and channel are connected before relying on Slack delivery.
Permissions and prerequisites
In-app notifications require a signed-in user and only expose context the user is allowed to access. Organization alert changes require the relevant administrative access. Slack delivery requires an active Slack integration and valid organization channel configuration.
An empty list does not necessarily mean there has been no activity; event coverage varies by module and workflow.
Guides planned for this module
- Review unread notifications and open related work.
- Filter notification history by module and read state.
- Mark one or all notifications as read.
- Understand notification severity and timing.
- Configure organization alert preferences.
- Connect supported module alerts to Slack channels.
- Troubleshoot missing in-app or Slack notifications.