Overview

In the context of the Notyfire platform, modules represent the primary functional pillars that categorise how information is tracked, visualised, and disseminated to users. The system is built around two main modules: Announcements and Development.

Purpose

The fundamental difference lies in the type of data they manage and the audience they serve within the organisation.

Feature
Announcements
Development

Primary Focus

Communication and Transparency. Focuses on high-level system changes, incidents, and business updates.

Technical Execution. Focuses on the software delivery lifecycle, specifically code builds and environment-specific deployments.

Content Examples

Incidents (e.g., "MoonApp unavailability"), changes ("VPN server upgrade") or business reports.

Software development events showing Application, Component, Version, and Environment (test, uat, prod).

Visualisation

Uses List, Calendar, and Status Board.

Uses Deployment logs and Environment Cards showing current versions in specific stages.

User Role Usage

Primarily used by Publishers to keep the whole company informed.

Primarily used by Developers and Service Accounts to track the CI/CD pipeline.

Subscription Logic

Filtered by announcement attributes like type, status or related systems.

Filtered by app and event types (Builds and Deployments).

Meaning of Modules

In Notyfire, modules are the distinct data streams that allow for granular control over different areas tracking. By separating the platform into these modules, Notyfire ensures that users are not overwhelmed by irrelevant data.

  • Bifurcated Workflows: The "Private Subscriptions" and "Team Subscriptions" pages are divided into these two categories so users can choose to receive urgent Announcements (like a server being down) without necessarily needing to see every technical Development update (like a version 1.0.1 being pushed to a test environment).

  • Shared Infrastructure: While the modules manage different data, they share the same notification channels. This means a user only needs to define their contact details once to receive notifications from either module.

  • Administrative Separation: Administrators manage these modules differently; Announcements use pre-defined Templates for standardised commmunicating, while Development tracks automated inputs from integrated Tools like Bitbucket, Jenkins, and Argo CD.

Last updated