Notifications
What this screen is for
Notifications is what the platform wants to tell you: deployments that finished, things that failed, and events on what you own.
Before you start
| To do this | You need |
|---|---|
| See notifications | the notifications read permission |
If the entry is absent from your sidebar, you do not hold that permission.
Opening it
- The notifications entry in the sidebar, below Fenwave Docs.
Direct URL: /notifications
The interface
📸 Screenshot Placeholder: The notifications list. Mark: (1) an unread notification, (2) its source, (3) the read/unread control.
| # | Control | What it shows | When you’d use it |
|---|---|---|---|
| 1 | Notification | One event | Reading |
| 2 | Source | What produced it | Deciding whether it matters |
| 3 | Read / unread | Marks it handled | Keeping the list meaningful |
A notification list nobody marks read stops being read at all. Treat unread count as a working queue rather than a badge to ignore.
Walkthroughs
Act on a notification
Read it, follow it to its source — a deployment, a release, an environment — and mark it read once you have dealt with it.
Scenario
Coming back from leave to a long notification list.
- Open notifications and scan for failures first, ignoring successes. A successful deployment from last Tuesday needs nothing from you.
- For each failure, follow it to its source and check whether it is still failing. Most will have been resolved by whoever was on duty, and marking them read is the whole action.
- For anything still broken, go to the relevant area — Deploy for environments, Deployments for releases.
- Mark everything you have handled as read, so the next person to look at your queue — including you tomorrow — sees a real signal.
- If a class of notification is never actionable for you, that is worth reporting. Notifications that are always ignored train people to ignore the ones that matter.
When it doesn’t work
| Symptom | Cause | How to check | Fix |
|---|---|---|---|
| No notifications entry in the sidebar | Missing the notifications read permission | Access Explorer | Ask for a role granting it |
| You receive nothing | Nothing you own has produced events, or notifications are not configured for that source | My Groups | Confirm your group owns the components you expect |
| You receive too much | You own more than you thought | Architecture filtered by owner | Review ownership with your team |
| A notification links somewhere you cannot open | Its target needs a permission you lack | Access Explorer | Ask for the permission |