Notification (Coming Soon)

Scoutflo’s notification system ensures you stay informed on critical updates, errors, alerts, product information, and reminders tailored to your workflow. Users have the flexibility to customize the types of notifications they want to receive, as well as the delivery channels (InApp, Email, Slack), and can control the notification settings at account and workspace levels. Here’s a detailed breakdown of the notification types, levels, and customization options available.


Notification Types

Each type of notification provides specific information with an optional call-to-action (CTA) or link for direct follow-up.

  • Alerts: In-process decision notifications, including data, CTA, and link.

  • Errors: Notifications about system errors, providing remediation steps, CTA, and optional link.

  • Information: General updates and optional CTA/link for further actions.

  • Product Updates: Important product changes, with data and link to update details.

  • Reminders: Timely notifications to encourage follow-up actions, including data, CTA, and link.


Notification Sources

Users can receive notifications from various sources within Scoutflo, depending on their role and actions taken at different levels.

  • Account Level: Notifications regarding account management.

  • Workspace Level: Notifications focused on specific workspaces.

  • Resource Level: Notifications about individual resources or services.

  • Platform Level: General platform notifications affecting all users.


Notification Nature and Criticality

Customize notifications based on their importance:

  • Nature:

    • Optional: Requires user subscription, typically for external integrations.

    • Default: Basic, essential notifications automatically enabled.

  • Criticality:

    • Critical: High-priority notifications that cannot be disabled, ensuring they reach the user.

    • Normal: General updates and information that users can opt in or out of.


Notification Triggers

Notifications are triggered based on specific events, allowing users to configure responses to essential events.

  • Trigger Types:

    • CRUD Success: Completion of actions like create, read, update, and delete.

    • CRUD Failure: Notification upon failure of CRUD actions.

    • Reminders: Regular follow-ups on pending actions.

    • News/Updates: Product announcements or updates.


Slack Integration for Critical Notifications

Scoutflo supports Slack integration, allowing users to receive critical notifications directly in Slack. A dedicated section on the notifications settings page provides a walkthrough to connect Slack by adding a Webhook URL, enabling real-time alerts for important actions and issues.


Notifications Settings Page

Scoutflo provides a dedicated Notifications Settings page where users can configure notification preferences. This page is organized into account and workspace-level settings, allowing detailed customization for each type of notification.

  • Slack Integration Section: Allows users to integrate Slack for notification delivery. Instructions are provided to help users set up Webhook URLs for seamless integration.

Scoutflo offers two main settings sections for notifications, each with its subcategories for organizing notification types and channels.

  1. Account-Level Notifications Located within the Account Settings, this section allows you to manage notifications for account-level events:

    • Sign-Up Notifications

    • GitOps Notifications

    • Billing Notifications

    • Product Updates Notifications

  2. Workspace-Level Notifications Found within Workspace Settings, this section focuses on workspace-specific notifications:

    • Workspace Notifications

    • IaC Notifications

    • Application Management Notifications

    • Invite Notifications


Triggers and Criticality Indicators

Each section lists specific triggers for notifications, with some marked as critical (denoted with an asterisk *). Critical notifications have default delivery options (InApp, Email, Slack) pre-selected and locked to ensure delivery.

Example Critical Triggers:

  • Critical Alerts: e.g., “Cluster failure.”

  • Critical Errors: e.g., “Deployment failure.”

Subscription Toggles for Delivery Methods

Users can enable or disable delivery methods for each notification, with the following options:

  • InApp: Notifications within the Scoutflo platform.

  • Email: Notifications sent to the user’s registered email.

  • Slack: Real-time notifications delivered via Slack (if integrated).

Critical notifications have fixed subscriptions for all delivery methods.


Additional Settings and Features

  • Search/Filter Option: It helps users quickly locate specific notifications or triggers (e.g., “Cluster failed”).

  • CTA Buttons:

    • Save: Save changes to notification preferences.

    • Discard: Discard any unsaved modifications.

    • Reset: Revert to Scoutflo’s default settings.

    • Select All: Enable all notification methods (InApp, Email, Slack) for selected triggers.


Scoutflo’s notification system is designed for ease of use, allowing users to configure and manage notifications efficiently across different channels and criticality levels. With full control over how and where notifications are received, users stay informed and responsive to critical changes, updates, and actions across their workflows.

Last updated