Notifications
Inbox is the first screen in the navigation. It holds four kinds of notification, and only these four:
| Kind | Sent when |
|---|---|
| Assigned to you | An issue is assigned to you |
| You were mentioned | Somebody writes @your-login in a comment Pealboard reads from GitHub |
| New request in a portal | A customer opens a request in a portal you manage |
| Sync gave up | A sync job failed and stopped retrying; admins only |
Selecting a notification opens the issue and marks it read. Mark all read marks every unread one. The unread count is shown as a number beside the Inbox, in tabular figures, and is refreshed every 60 seconds.
Email is sent for the same four kinds, to the same people, and cannot be turned off yet. Per-member switches — Email notifications and Daily email digest — are not in this release: there is no API route that reads or writes a member’s notification preferences, so Settings → Notifications states what is sent rather than offering a switch that would change nothing.
Email about issues you follow in GitHub continues to come from GitHub, on GitHub’s own settings. Pealboard does not intercept or duplicate it.
One outgoing webhook per workspace, in Settings → Integrations. Settings → Notifications links to it.
- Create an incoming webhook in Slack and copy its URL.
- Paste it into Webhook URL. It must be on
hooks.slack.com; any other host is refused. - Select Send a test message to confirm it arrives.
- Choose which of the four kinds are sent.
Pealboard stores the URL and never returns it. The screen shows the host and the last four characters of the path, which is enough to recognize which URL is stored and not enough to post to it.
Messages are one line each, naming what happened. There are no buttons in them: this is an outgoing webhook, not a Slack app, and nothing can be done from inside Slack. A Slack app with slash commands is not part of this release.
If a test message is refused, Slack’s own reason is shown. no_service means
the webhook was revoked in Slack and channel_not_found that the channel was
archived; both are fixed by pasting a new URL.
What customers get
Section titled “What customers get”A portal customer is emailed when a request’s status changes and when a new public comment is added, unless they unsubscribed from that request with Stop emailing me about this request. Customers have no Inbox and no Slack.