Nullgap.dev Docs

Integrations

E-mail

Every e-mail Nullgap sends, when it sends it, who receives it and what is never put in an e-mail.

Nullgap sends the e-mails listed on this page and no others. There is nothing to connect: e-mail is part of the service, and an installation without e-mail set up sends none of them. This page tells you what to expect in an inbox, so you can recognise a genuine message and set up filters.

#What is sent

E-mailSent whenTo whom
Sign-in linkSomeone asks for a link on the sign-in pageThat address, and only if it belongs to a member of an organisation or has a pending invitation
InvitationAn admin or owner invites someone under People, or support sends an invitation againThe invited address
Workspace readyNullgap sets up a workspace for youThe workspace's first owner
Workspace reminderThree days after "Workspace ready", if nobody has opened the workspace yet. Sent onceThe workspace's first owner
First review readyThe workspace's first pull request review finishes. Sent once per workspaceOwners and admins
First pentest finishedThe workspace's first pentest finishes. Sent once per workspaceOwners and admins
Fix run resultA fix run started by an automation finishesThe addresses listed on that automation, all members of the workspace
Support request receivedYou open a support requestThe person who opened it
Support repliedNullgap support answers a requestThe person who opened it
Support asks for accessNullgap support asks to look at the workspaceOwners and admins
Ownership change pendingNullgap support starts making someone an owner, at your organisation's requestEvery current owner, and the person who is to become one
Workspace deletedThe workspace is deleted, by an owner or by Nullgap operationsEvery owner at the time

Subject: "Your Nullgap sign-in link".

  • The link works once and expires after 15 minutes.
  • A link is sent only to an address that can already get in: a member of an organisation, or someone with an invitation that has not expired. For any other address nothing is sent. The sign-in page gives the same answer either way, so it cannot be used to find out who has an account.
  • At most three links are sent to one address in 15 minutes. Further requests in that time are answered the same way and send nothing.
  • If you did not ask for the link, ignore the message. Nobody is signed in until the link is opened, and an account with multi-factor sign-in still asks for the second factor after it.

See multi-factor sign-in and passkeys and single sign-on for the other ways to sign in.

#Invitations

Subject: "You have been invited to organisation name on Nullgap".

  • The message names who sent the invitation and links to the page that accepts it.
  • The link expires after 7 days.
  • The same link is shown once in the console to the person who sent the invitation, so it can be passed on by another channel if the e-mail does not arrive.

See people and roles.

#Workspace ready and the reminder

When Nullgap sets up a workspace for you, its first owner receives "Your Nullgap workspace for organisation name is ready", with a link that accepts the invitation. The link works once and the message says when it expires.

If nobody has opened the workspace three days later, one reminder follows: "Reminder: your Nullgap workspace for organisation name is waiting". It carries a new link; the first one keeps working until its own expiry. There is no second reminder.

#First results

Once per workspace, owners and admins receive:

  • "Your first Nullgap review is ready", naming the repository and the pull request, with a link to the review;
  • "Your first Nullgap pentest has finished", naming the repository and the number of findings by severity, with a link to the pentest.

Neither contains a finding. Later reviews and pentests send no e-mail.

#Fix run results

When you create or edit an automation, the Email field takes a comma-separated list of addresses, up to 20. Each address must belong to a member of the workspace: the field refuses any other. When a fix run started by that automation finishes, each address receives one message.

Subject: "Remediation outcome: finding title", where the outcome is fixed, no fix needed, false positive or failed; or "Fix proposed, not proven: finding title" when the automation allows unproven fixes and the flaw could not be reproduced.

The body has two lines and one link:

  • the repository, the finding's severity and its title;
  • one sentence for the outcome: a verified fix is ready for review, a fix was proposed but not proven (a draft for a person to review), no change was needed, the finding could not be exploited and was marked a false positive, or the run did not produce a verified fix;
  • a link to the pull request when one was opened (a draft pull request for an unproven fix), otherwise to the finding in the console.

A fix run that you start by hand has no automation and therefore sends no e-mail. A fix run that is stopped by an error sends none either.

#Support

Each message of the support channel is a short notice and a link back to the console:

  • "Nullgap support: we have your request (id)" when you open a request;
  • "Nullgap support replied to your request (id)" when support answers. The reply itself is not in the e-mail;
  • "Nullgap support is asking for access to your workspace" to owners and admins, saying whether support asked to read only or also for support actions, and for how long. Nothing is opened unless one of them approves it in the console. A request nobody answers lapses after 72 hours.

None of them carries the subject or the text of a request, and answering one of them reaches nobody: reply in the console.

#Ownership change

When Nullgap support starts making someone an owner of the workspace at your organisation's request, every current owner receives "An ownership change is pending on your Nullgap workspace" and the person who is to become an owner receives "You are about to become an owner of a Nullgap workspace". The message says when the change takes effect; any current owner can cancel it under Settings before then.

#Workspace deleted

When a workspace is deleted, every owner at the time receives "The Nullgap workspace name was deleted": who deleted it and when, what was removed, what is kept, and until when nobody else can register its address. See deleting a workspace.

#What is not sent by e-mail

  • Review and pentest results, after the first of each. Use Slack channel notifications or outbound webhooks for those.
  • New findings. There is no e-mail per finding and no digest.
  • Anything to the privacy and incident contacts. The two contact addresses under Settings, Data protection are stored and shown in the console. The product does not send automated e-mail to them.
  • Alerts about account activity, such as a new API key or a changed setting. Those are recorded in the audit log.

#What is never put in an e-mail

  • Source code, code excerpts or diffs.
  • A finding's description, its proof or evidence, or remediation advice.
  • The subject or text of a support request or reply.
  • Passwords, API keys, signing secrets or tokens of any integration. The only secret an e-mail ever carries is a single-use link itself (a sign-in link or an invitation link).
  • Attachments.

A fix-run e-mail does contain the finding's title, its severity and the repository name. If those are sensitive for you, leave the automation's Email field empty and use webhooks instead.

#Recognising a genuine message

  • Every link points to the address of your Nullgap console and nowhere else.
  • No message asks you to reply, or to send a password, a code or a key.
  • Each message is sent as both plain text and HTML with the same content.

#If an e-mail does not arrive

SituationWhat to do
No sign-in linkCheck that you typed the address you were invited with. Wait 15 minutes if you asked more than three times. Otherwise sign in with a passkey or through single sign-on if your organisation uses them.
No invitationAsk the person who invited you for the link shown in the console, or have them remove the invitation under People and send it again.
No fix-run messageCheck the address list on the automation, and that the run was started by that automation and finished.
No support noticeOpen Help, My requests: every request and reply is there whether or not the e-mail arrived.

Delivery failures are not retried and are not shown in the console.

Nullgap documentation