Nullgap.dev Docs

Administration

People and roles

Invite people to your organisation, choose what each of them may do, and manage pull request review seats.

Everyone who uses Nullgap for your organisation is a member with one of three roles: owner, admin or member. This page says what each role may do, how people join and leave, and how review seats work.

In the console, people are managed on the People page.

#The three roles

A role belongs to a membership, not to a person: the same account can be an owner of one organisation and a member of another.

RoleIntended for
OwnerThe people accountable for the organisation: sign-in set-up, API keys, data export and erasure
AdminThe people who run it day to day: repositories, pentests, settings, people
MemberEveryone who reads and triages findings

The person who creates an organisation is its first owner.

#What each role may do

Each row lists what a role adds to the one above it.

RoleMay do
MemberRead everything in the organisation: findings, reviews, pentests, reports, repositories, applications, settings, people, pending invitations, the audit log, usage and billing, and the list of API keys (never a key's secret). Triage findings, one at a time or in bulk, and add notes. Start a fix for a finding and create an issue from it. Ask for a review of a pull request. Ask for a pentest estimate. Edit an application's context and regenerate its threat model. Check a package against the dependency rules
AdminChange the organisation's name, address and settings. Invite people, remove members who are not owners, change roles between admin and member, and assign or remove seats. Connect GitHub, add, enable and remove repositories, upload archives. Create and delete applications. Start, cancel and retest pentests and manage pentest schedules. Manage automations, custom checks, integrations and outbound webhooks. Share a report by link. Verify and export the audit log. See how single sign-on and SCIM are set up. See and retry background jobs. Sign everyone out. Start the trial
OwnerGive or take away the owner role, invite an owner, remove an owner. Create, rotate and revoke API keys. Set up, change and remove single sign-on, verify e-mail domains, and turn SCIM provisioning on or off. Connect GitLab, Bitbucket Cloud, Azure DevOps and GitHub Enterprise Server, and rotate a connection's webhook secret. Set up the Slack assistant. Export everything and erase data

Some of these actions also ask for a fresh second-factor check. See the step-up check.

#What an API key may do

An API key acts for the organisation, not for a person, and never as an owner.

Key scopeActs as
readA member who can only read
writeA member
adminAn admin, except for actions that need a fresh second-factor check

Every owner action refuses every key, and so does any action that asks for a step-up check (changing a role, for example). See API keys.

#Invite someone

You need to be an admin. To invite an owner you need to be an owner.

  1. Open People and choose Invite.
  2. Enter the person's e-mail address and pick a role.
  3. Send the invitation.

Nullgap creates a single-use link and shows it to you once. The link is also e-mailed to the person when the service has outgoing mail configured. If you are not sure it is, copy the link from the confirmation and pass it on yourself.

The invitation is listed under Pending invitations until it is accepted, revoked or expired. An address has at most one pending invitation: inviting it again replaces the earlier one, and the earlier link stops working. An address has at most one pending invitation: inviting it again replaces the earlier one, and its link stops working.

FactValue
LifetimeSeven days from creation
UsesOne
Who can acceptOnly an account whose e-mail address is the invited address
Already a memberRefused with 409 already_member

Through the API, with a key that has the admin scope:

curl -s -X POST -H "Authorization: Bearer $NULLGAP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email":"dana@acme.example","role":"member"}' \
  "$NULLGAP_URL/api/orgs/$NULLGAP_ORG/invitations"
{
  "id": "inv_8f2k1m",
  "email": "dana@acme.example",
  "role": "member",
  "invitedBy": "api-key:CI pipeline",
  "createdAt": "2026-11-16T09:30:00.000Z",
  "expiresAt": "2026-11-23T09:30:00.000Z",
  "acceptUrl": "https://nullgap.acme.example/invite/..."
}

acceptUrl is returned only here. It is not stored in a readable form, so it cannot be shown again: revoke the invitation and create a new one if it is lost.

#Accepting an invitation

The invited person opens the link, signs in with the invited address, and accepts. They join with the role on the invitation.

What can go wrong:

What you seeWhyWhat to do
404 invalid_invitationThe link was already used, was revoked, or is older than seven daysSend a new invitation
403 "This invitation was sent to a different email address"The signed-in account has another addressSign in with the invited address, or invite the address the person uses
403 sso_sessionThe person is signed in through single sign-on. Such a session cannot accept invitationsSign in with an e-mail link or a passkey, then open the link again

People who join through single sign-on or SCIM do not need an invitation.

#Change a role

On People, choose a new role in the Role column. Through the API it is PATCH /api/orgs/:org/members/:userId with {"role":"admin"}; see the people reference.

  • Changing a role asks for a fresh second-factor check, so an API key cannot do it.
  • Only an owner can make someone an owner or change an owner's role.
  • The last owner cannot be demoted. See the last-owner rule.

#Remove someone

On People, choose Remove next to the person. An admin can remove admins and members. Only an owner can remove an owner.

Removing a member:

  • ends their membership at once: their sessions can no longer open the organisation;
  • releases their review seat;
  • removes the link between their account and their Slack user, if they had one.

It does not delete the person's account: an account belongs to the person and may be a member of other organisations.

#The last-owner rule

An organisation always has at least one owner. Demoting or removing the only owner is refused with 400 last_owner ("An organisation needs at least one owner"). Make someone else an owner first.

SCIM follows the same idea more strictly: it never deactivates or removes any owner. See SCIM provisioning.

#Review seats

A PR review seat belongs to one member of the workspace. Only members take a seat. Seats do two things:

  • they are the unit your plan counts;
  • each seat adds a fixed number of reviews a month to a pool shared by the whole organisation. See usage.

#Who gets a seat

  • The person who creates the workspace holds its first seat.
  • The Review seat switch on People assigns or removes the seat of a member.
  • A member who has linked their code-host login (below) is given a seat automatically the first time a pull request of theirs is about to be reviewed. The audit log records seat.assigned.

A seat stays with the member when they link or change their code-host login.

#Pull requests from people who are not members

Pull requests from bots and outside contributors are reviewed as well. They take no seat: their reviews are drawn from the pool that the members' seats make up. To stop reviews for particular authors, use review filters.

A member's seat is removed when the member is removed or deprovisioned through SCIM.

Each person links their own login, on their profile (/settings/profile in the console):

  1. Open your profile.
  2. Enter your username in GitHub username, without @.
  3. Save.

The value must look like a GitHub username: letters, digits and single hyphens, at most 39 characters, optionally ending in [bot]. Nullgap compares it, ignoring case, with the author login of each pull request. On another code host the match works only if your login there is written the same way.

Signing in with GitHub fills the field in for you.

#List people through the API

Any API key can read the member list:

curl -s -H "Authorization: Bearer $NULLGAP_API_KEY" \
  "$NULLGAP_URL/api/orgs/$NULLGAP_ORG/members"
[
  {
    "userId": "usr_4k2p9x",
    "email": "dana@acme.example",
    "name": "Dana",
    "githubLogin": "dana-acme",
    "role": "admin",
    "seat": true,
    "lastActiveAt": "2026-11-16T08:12:44.000Z",
    "joinedAt": "2026-10-02T14:03:10.000Z"
  }
]

seat says whether the member holds a seat under their linked login (or under their account, when no login is linked). Pending invitations are at GET /api/orgs/:org/invitations. The full field lists are in the people reference.

#What is recorded

Every change on this page is written to the audit log: invitation.created, invitation.accepted, invitation.revoked, invitation.replaced, member.role, member.removed, seat.assigned and seat.removed.

Nullgap documentation