Notification Management
It's tedious to manually check every time whether a build is complete or a deployment succeeded. With KIOPS's notification system, you can know immediately when important events occur.
KIOPS notifications are delivered only through the in-app notification drawer opened from the bell icon in the top right of the header. External channels such as Slack, email, and browser push notifications are not confirmed in code, so this guide focuses on the in-app flow.
Notification System Overview
KIOPS provides notifications via the bell icon in the top right of the screen.
- Notification icon: Click the bell icon on the right side of the header to open the notification drawer.
- Unread badge: If there are unread notifications, a red number badge appears on the icon.
- Notification drawer: Clicking the icon slides open a list of recent notifications from the right side of the screen.
Notification Types (type)
KIOPS notifications use the following type values in code (the type definition declares five values: organization_invite / membership_request / system / pipeline / other. pipeline exists only in the type definition; actual pipeline notifications are represented as the system type plus data.stage).
organization_invite
Notification delivered to an invited user when an organization administrator sends an invitation.
- While
pending, shows Accept / Reject buttons. - Once answered, the status changes to
acceptedorrejected.
membership_request
Notification delivered to organization administrators when someone requests to join.
- A new join request has arrived (while
pending, shows Approve / Reject buttons) - Once resolved, the notification only exposes the Mark as read action.
system
KIOPS's pipeline stage notifications are delivered with this type. For each of the seven pipeline stages, separate notifications are sent for started/completed/failed states. Only the Mark as read action is exposed.
other
Anything that doesn't fall into the three types above. Some operational notifications may be classified as other, exposing only the Mark as read action.
- Critical/High vulnerability alerts and security scan completion alerts
- Incident occurrence/resolution alerts (incidents live on the service detail page → Quality Management tab)
- System maintenance announcements
- Rollback completion alerts
Pipeline Notifications (system type)
system type notifications are sent per pipeline stage. KIOPS pipelines consist of the following seven stages.
| stage | Description |
|---|---|
| source | Source code fetch stage |
| sast | Static analysis (SAST) stage |
| build | Docker image build stage |
| sca | Dependency analysis (SCA) stage |
| deploy | Deployment stage |
| operation | Operation stage |
| dast | Dynamic analysis (DAST) stage |
stage × stageStatus Matrix
Each stage can have one of three stageStatus values, and each combination is sent as a separate notification.
| stage | started | completed | failed |
|---|---|---|---|
| source | source fetch started | source fetch completed | source fetch failed |
| sast | SAST analysis started | SAST analysis completed | SAST analysis failed |
| build | build started | build completed | build failed |
| sca | SCA analysis started | SCA analysis completed | SCA analysis failed |
| deploy | deployment started | deployment completed | deployment failed |
| operation | operation started | operation completed | operation failed |
| dast | DAST scan started | DAST scan completed | DAST scan failed |
Failure (failed) notifications include an errorMessage field. Expand the details toggle in the drawer to see the cause.
Notification status (4 values)
Each notification has a status value representing its handling state.
- pending: Awaiting response (for organization invite / request notifications)
- accepted: Invite accepted or request approved
- rejected: Invite rejected or request denied
- read: A regular notification has been marked as read
Viewing Notifications
Step 1: Open the Notification Drawer
- Find the bell icon in the top right of the screen.
- If there are unread notifications, the count is shown as a red badge.
- Click the icon to slide open the notification drawer from the right.
Step 2: Review the Notification List
Information available in the list:
- Title / content: What the event is and its detailed description
- Time: When the notification was generated (e.g., "5 minutes ago")
- Related service: For pipeline notifications, the service name is shown
- errorMessage details toggle: Expand it on failure notifications to inspect the cause
Step 3: Respond to Notifications
The action buttons depend on the notification type and handling status.
- organization_invite (pending): An organization invitation delivered to the invited user - shows Accept / Reject buttons. Responding changes status to
acceptedorrejected. - membership_request (pending): A join request delivered to an admin - shows Approve / Reject buttons. Responding changes status to
acceptedorrejected. - system / other / already-resolved notifications: Only the Mark as read text button is shown. Clicking it changes status to
read. - Mark all as read: The "Mark all as read" button at the top of the drawer marks all regular notifications as read in bulk.
type x action mapping
| type | Actions shown |
|---|---|
| organization_invite | Accept / Reject |
| membership_request | Approve / Reject |
| system / other | Mark as read |
The row itself has no click handler; only the action buttons (Mark as read / Accept / Reject / Approve) and the failure details toggle are interactive.
Notification cleanup is done only via Mark as read or Mark all as read actions. KIOPS does not expose a manual per-notification delete UI.
Real-World Usage Scenarios
Scenario 1: Responding to a Build Failure
After pushing code, you were working on something else when a red badge appeared on the notification icon.
Response sequence:
- Click the notification icon to open the drawer.
- Find the "Build Failed: my-service" notification (stage=build, stageStatus=failed).
- Expand the details toggle on the row to inspect the errorMessage.
- The row itself does not navigate, so open the service detail directly from [Dashboard] or [Service Management] in the side menu.
- Review additional information in the build log, then fix the code and rerun the build.
Scenario 2: Monitoring Deployment Progress
You started a deployment and want to be notified of progress while working on other things.
Monitoring sequence:
- When the deployment starts, a stage=deploy, stageStatus=started notification arrives.
- When it completes, a stage=deploy, stageStatus=completed notification arrives.
- On failure, a stage=deploy, stageStatus=failed notification arrives — expand the errorMessage details to inspect the cause.
Best Practices
Efficient Notification Management
- Prioritize failure notifications: Regardless of stage, expand the errorMessage details on any stageStatus=failed item.
- Mark as read: Mark regular notifications as read once handled.
- Use Mark all as read: When notifications accumulate, clear them in bulk with the top button.
Team Collaboration
Membership requests must be responded to quickly by the responsible admin. Make the owner explicit.
- When a pipeline failure notification arrives, the on-call engineer should inspect the errorMessage and share it on the team channel.
- Membership request notifications should be answered promptly with Approve/Reject.
Troubleshooting
Notification badge is not displaying
Possible cause: Browser cache issue.
Solution:
- Refresh the page (F5)
- Hard refresh (Ctrl+Shift+R)
Notification drawer does not open
Possible cause: Temporary UI issue.
Solution:
- Refresh the page.
- If the problem persists, try a different browser.
- If it still does not work, contact the administrator.
Related Guides
- Dashboard Usage - The service status table and detail page
- DORA Metrics - DevOps indicators on the Quality Management tab