Skip to content

Organization quickstart

Set up a new Vulnesis organisation, invite a colleague, create a service account for CI, and give the pipeline VULNESIS_ORG_ID and VULNESIS_API_KEY.

Updated 04 Nov 2026Markdown

This page sets up an organisation for a team: one colleague invited, and a credential CI can use that belongs to the organisation rather than to a person.

Prerequisites

  • A console sign-in at https://www.vulnes.is/resolve with your company address. The first person to sign up with a company domain becomes the owner of that domain’s organisation. A free-mail address gets a personal organisation that nobody can join.
  • The owner role for steps 2 and 3. Every plan includes members and service accounts.

1. Open the Members page

Go to Account › Members (/resolve/members). It lists the people, service accounts, pending invitations and access requests.

2. Invite a colleague

Choose Invite person. In Invite someone, enter the Email address, pick a Role (member, developer or owner), and choose Send invitation.

The invitation lasts 14 days. The colleague signs up or signs in with that address and joins with that role. Someone from your domain who signs up without an invitation waits as an access request until you approve them.

3. Create a service account for CI

Choose New service account. Enter a Name, for example ci-scanner, and under What it may do keep Member to scan, upload and read. Choose Create.

The account is named <org>:ci-scanner. The next dialog shows its Org ID, Secret and API Key once. Copy the Org ID and API Key now: the secret cannot be shown again, only rotated.

4. Give the pipeline the credential

Save the two values as CI secrets and pass them to the CLI as environment variables. In GitHub Actions:

- name: Vulnesis scan
  env:
    VULNESIS_ORG_ID: ${{ secrets.VULNESIS_ORG_ID }}
    VULNESIS_API_KEY: ${{ secrets.VULNESIS_API_KEY }}
  run: vulnetix scan

The variables take precedence over any stored login.

5. Check the credential

VULNESIS_ORG_ID=<org id> VULNESIS_API_KEY=<api key> vulnetix auth verify
[OK] Authentication verified successfully
  Organization: <org id>

A wrong key fails with verification failed. A deactivated account is refused with 403.

Next

esc
↑ ↓ move↵ openSearches in your browser. A key like autonomy.max or a code like threshold_required jumps straight to it.