Administration
Notifications
The Notifications tab is a grid: your members down one side, the five kinds of alert across the top, and a switch in every cell. Set the workspace default there, and override it for a repository that needs different people.
Setting who is emailed is an admin task. New members start on a sensible default for their role until someone changes it here.
#The five kinds of alert
Notifications
Choose which members are emailed for each kind of alert — workspace-wide, with per-repository overrides where you need them — and connect Microsoft Teams channels for chat delivery. New members inherit a sensible default by role until you change it here.
Workspace defaults
Who receives each kind of alert, everywhere — unless a repository below overrides it.
| Member | Security | Compliance | CI/CD | Pentest | Digest |
|---|---|---|---|---|---|
| Huud Ahmad | |||||
| Rojitha Perera | |||||
| Sam Okafor |
Repository overrides
Microsoft Teams
| Kind | What it covers |
|---|---|
| Security | Vulnerability exposures and critical security findings. |
| Compliance | Vendor-agreement coverage and BAA expiry. |
| CI/CD | GitHub Actions failures and reliability. |
| Pentest | Validated offensive-security findings. |
| Digest | The engineering digest (weekly or daily), workspace-wide. |
Each column has a tooltip naming the individual alerts folded into it, so you can see that Security covers a confirmed exposure, the daily digest and a critical GitHub-native alert before you switch anyone on.
#Setting the workspace defaults
A switch in a cell decides whether that person is emailed for that kind of alert everywhere. The column header also has a control that subscribes or unsubscribes everyone at once, which is the quick way to set up a column and then take two people back out.
A member you have never set a switch for sits on a default worked out from their role, so a new admin starts subscribed to more than a new developer does. Setting a switch replaces that default for good. See Roles and permissions.
#Overriding for one repository
Repository overrides gives a repository its own recipient list for a kind of alert. Each cell reads Default with a count while it inherits, and Custom with a count once you have set it.
This is what you reach for when one repository has a different owner from the rest: security alerts on the payments service can go to the two people who look after it, while everything else stays on the workspace default.
A repository appears in the list once it is enabled for at least one kind of alert.
#Microsoft Teams
Microsoft Teams connects a channel so alerts arrive in chat as well as by email. Connect the channel, and the same categories decide what arrives there.
Teams channels are included with Pro. See Plans and billing.