Notifications
Putnami tells you when a CI run fails, a deploy succeeds, a change waits for approval, or your pull request is blocked or merged, without you watching the console.
Two channels carry these events. A workspace posts to one Slack channel, and
each person gets browser notifications on their own devices. You set both on
the Notifications page of the console, at putnami.app: open the menu
under your avatar, then choose Notifications. No CLI command sets them.
Events
| Event | Sent when | The link opens |
|---|---|---|
| Red CI runs | A CI run fails or times out | The run |
| Successful deploys | A release is live in an environment | The environment on the Live tab |
| Changes waiting for approval | A run waits for a person to approve a declaration | The change, where you review and approve it; older events without a full commit identity open the run |
| Pull requests blocked on a gap | A pull request's verdict waits for gaps to be accepted or fixed | The change, where you review the gaps |
| Merged pull requests | A pull request merges, by a person or by auto-merge | The change |
Each event is sent once per Slack channel and once per device, even when Putnami receives it twice. A canceled or skipped run sends nothing. You approve in Putnami, signed in, after opening the notification's link.
Messages start with a status icon: ❌ for failed CI, 🚀 for a live deploy,
⏳ for an approval, 🚧 for a blocked pull request and ✅ for a merged one. Slack separates the status, repository or environment,
details and action onto their own lines. Browser notifications show the status
in the title and the details in the body. Deploy messages name the environment
and affected projects; CI, approval and blocked messages explain what to do
next. Approval and blocked messages also say the verdict and how many required
gates passed, such as Gates: 5 of 5 passed.
When the associated pull request is available, messages show its title and number, its author, and the titles of up to five linked issues. Slack links the PR title to its change in Putnami and each issue to GitHub. If that context is unavailable, the repository and commit identify the event instead. The same notification is still delivered.
Slack
A workspace administrator connects one Slack channel through a Slack incoming
webhook. You need the platform.workspace.manage permission on the
workspace; a workspace admin holds it.
- In Slack, create an incoming webhook for the channel that should get the
messages. Slack gives you a URL that starts with
https://hooks.slack.com/services/. - On the Notifications page, paste the URL into Webhook URL, check the events to post, and choose Save. A first save checks every event.
- Choose Send test message. The page shows whether Slack accepted it, Slack's status, and the start of Slack's answer.
The webhook URL is a secret. Putnami stores it encrypted, never shows it
again, and never writes it to a log. The page shows only its host and last
four characters, such as hooks.slack.com/...a1b2. To change the URL, paste
a new one and save; leave the field empty to keep the current one.
Every member of the workspace reads whether Slack is set and which events it posts.
Browser notifications
Browser notifications follow a person, not a workspace. They show as system notifications, even when the console tab is closed.
- On the Notifications page, in the This device card, choose Turn on notifications on this device.
- Allow notifications when the browser asks. The page asks only when you click, never when it loads.
- The device appears under Your devices. The first time, every event you may receive in this workspace is turned on. On a later device, your choice stays as it is.
Repeat the steps on each browser and device. You can have up to 10 devices.
On an iPhone or iPad, add putnami.app to the Home Screen first, then open it
from there: Safari shows web notifications only for a Home Screen app.
You can install the console as an app on any device:
| Browser | To install |
|---|---|
| Chrome | Choose Install Putnami in the address bar. Chrome then shows Open in app on every putnami.app page. |
| Safari on iPhone or iPad | Share › Add to Home Screen. |
| Safari on a Mac | File › Add to Dock. |
The checkboxes in the card choose which events you get from this workspace, on all your devices. Choose Save after a change. Each workspace keeps its own choice, and every event starts off.
Who receives what
A browser notification reaches you only while you still hold the right to see its event. Putnami checks your rights each time it sends, so a person who loses access stops receiving at once.
| Event | Needs on the workspace | Roles that hold it |
|---|---|---|
| Red CI runs | platform.workspace.read |
Viewer, member, admin |
| Successful deploys | platform.workspace.read |
Viewer, member, admin |
| Changes waiting for approval | platform.workspace.manage |
Admin |
| Pull requests blocked on a gap | platform.workspace.read, and you opened the pull request |
Viewer, member, admin |
| Merged pull requests | platform.workspace.read, and you opened the pull request |
Viewer, member, admin |
Blocked and merged pull requests reach only the browsers you turned on while signed in with GitHub, matched to the pull request's author. A browser you turned on before these events existed gets them after you turn it on again.
Organization admins and tenant owners hold both permissions through the roles they inherit.
A person who may not manage the workspace sees the approval checkbox disabled, with the reason. Slack posts every checked event to the channel, whoever reads it there.
Turn notifications off
| Want to… | Do this |
|---|---|
| Stop one event from this workspace on all your devices | Uncheck it in This device, then Save |
| Stop notifications on the browser you are using | Turn off on this device |
| Stop notifications on a shared computer | Sign out. Signing out turns notifications off in that browser first |
| Stop notifications on another device | Remove next to it under Your devices |
| Stop notifications in a browser | Block notifications for putnami.app in the browser's site settings; Putnami deletes that device on its next send |
| Stop one event in Slack | Uncheck it on the Slack card, then Save |
| Stop all Slack messages | Remove on the Slack card, then confirm. The stored URL is deleted |
Signing out turns notifications off only when JavaScript runs in the browser. Where it does not, choose Turn off on this device before you sign out.
To turn notifications back on in a browser where you blocked them, set Notifications to Allow in the site settings, reload the page, then choose Turn on notifications on this device.