Bermward

Organization and alerts

Who your workspace is, how each person hears about problems, and who gets woken up when something breaks.

Notification preferences

Each person chooses, per event type, one of: Off, In app, In app + email, In app + daily digest. The bell in the app shows in-app notifications, and repeated events of the same kind are grouped so a noisy night does not fill the list.

EventWhat it meansDefaultWho gets it
Teammate joined member.joinedSomeone accepted an invite to your organization (admins).In appAdmins
Access requested access.requestedSomeone asked to join your organization (admins).In app + emailAdmins
Exposure changes exposure.findingsA scan of a monitored domain found new issues or assets, or confirmed issues are fixed.In app + emailEveryone in the workspace
Domain scan failed exposure.scan_failedA scheduled scan of a monitored domain could not finish.In appEveryone in the workspace
Downtime alerts uptime.incidentA monitor went down or recovered.In app + emailEveryone in the workspace
Monitor suggestions uptime.suggestionsA domain scan found public services that aren't monitored yet.In appEveryone in the workspace
Monthly report report.monthlyLast month's security and uptime report is ready (admins).In app + emailAdmins
Payment problems billing.payment_failedA subscription payment failed and needs a new card (admins).In app + emailAdmins
Leaked credentials credentials.exposedA staff address turned up in a new breach, or an infostealer infection was found for one of your domains.In app + emailEveryone in the workspace
Email spoofing alerts dmarc.alertDMARC reports show someone sending mail as your domain, or a legitimate sender failing authentication.In app + emailEveryone in the workspace
Compliance answers due compliance.attestation_dueSelf-attested compliance answers are about to expire and need confirming again (admins).In app + emailEveryone in the workspace
Dependency advisories dependencies.advisoriesA repository scan found new critical or high advisories, or an accepted risk expired and reopened (admins).In app + emailAdmins

On-call schedule

Phone alerts follow a schedule you set: time zone, days of the week, working hours, optional quiet hours, a primary contact and a secondary contact. If an incident is still open after the escalation delay (between one minute and 24 hours), the secondary contact is paged, including after quiet hours end. Contacts are the phone numbers you add on the Uptime page. See Uptime and alert credits.

Ticket destination

Admins choose where tickets are sent: an email address, or a Jira project. Jira needs the site, project key, the account email and an API token.

Setup checklist

The onboarding card on Overview tracks the first domain, reviewed findings, monitors, alert channels, DMARC, client creation (MSP) and a published status page. Admins can dismiss it for the workspace.

Workspace usage

API

MethodPathRoleWhat it does
GET/api/orgs/:orgId/notificationsviewerYour notifications. Query: limit, before, unread.
POST/api/orgs/:orgId/notifications/readviewerMark notifications read.
GET/api/orgs/:orgId/oncallviewerSchedule and contacts.
PUT/api/orgs/:orgId/oncalladminSave the schedule.
GET/api/orgs/:orgId/uptime/contactsadminPhone contacts for SMS and voice.
POST/api/orgs/:orgId/uptime/contactsadminBody: kind (sms or voice), phone in international format, label.
DELETE/api/orgs/:orgId/uptime/contacts/:contactIdadminRemove a contact.
PUT/api/orgs/:orgId/ticketsadminBody: kind (email or jira) and config.
GET/api/orgs/:orgId/usageadminWorkspace usage summary.