First run & onboarding
A quick-reference checklist for the first hour after your instance is up. If you
have not installed yet, start with the
full install guide — this
page assumes /healthz and /readyz
already return 200.
Create your organization
On the login screen, choose Create an organization; the first user becomes
the Organization Administrator. On a private instance
(REGISTRATION_ENABLED=false, the production default —
see the install guide),
self-service signup is disabled and this link is hidden: only the very first
(bootstrap) account can be created this way. The one-line installer creates this
first admin + organization for you automatically as part of install; everyone else
is added by invite (step 3).
Onboarding wizard
Open Home (/home) — the onboarding checklist is
there. There is no separate /onboarding page; this
guide used to name one (client finding D-11). (permission
onboarding:manage — admin and security manager roles have
it). Four steps:
- Frameworks & company profile — pick which of NIS2, ISO/IEC 27001:2022 and GDPR apply (at least one; all are optional), and enter legal name, country, sector, employees and revenue.
- NIS2 scope (only if NIS2 was selected) — answer the sector/size/ special-provider questions for a decision-support result (in-scope yes/no, entity type, confidence, reasoning). This is not a legal determination.
- Cyber maturity baseline — yes/partial/no questions that seed your initial maturity scores.
- Finish — derives the control libraries from your chosen frameworks and initializes a control assessment for every control. You can enable or disable a framework later from the Controls page.
GET /onboarding/status returns onboarding_completed: true and controls_initialized: true. /controls now shows a populated library.
Invite your team
Settings → Members, or POST /orgs/current/members.
Assign each person one of the five system roles. Full detail (permission matrix,
guardrails, SSO/SCIM) is on the dedicated
Users & roles
page — the short version: at minimum, invite one admin
(with MFA on) and one security_manager (CISO); add
it_manager, auditor and
executive as your team needs them.
Configure the platform
Under Settings: organization profile, branding (accent colour, login tagline, report footer), email/SMTP (with a "send test email" check), notifications (including an optional weekly readiness digest), threat intelligence (opt-in CISA KEV auto-flagging), webhooks and API tokens (admin-only — see the permission matrix), and — for Enterprise — SSO/SAML/OIDC/LDAP and SCIM provisioning (see Enterprise SSO, MFA & SCIM).