First-time setup
Create the initial administrator, choose an authentication path, and prepare the first organization and scan.
Complete this guide after Docker Compose or Helm is healthy. It is intentionally independent of the deployment platform.
1. Choose the administrator path
Choose one of these supported first-account flows:
- Local authentication: register the first account through the JustScan sign-up screen. The first local account in an empty database becomes the platform administrator.
- OIDC authentication: configure an identity provider before first login and map an identity-provider group or role to the JustScan administrator role.
Do not disable every recovery path until an administrator can sign in through the public hostname.
2. Confirm platform access
After signing in as an administrator:
- Open Administration → Users and create or verify the platform accounts that need system-wide access.
- If local self-service sign-up is not part of your operating model, disable it after the intended administrators and users have been created.
- Keep a second tested administrator or a tested OIDC administrator recovery path.
3. Create shared security context
Create an organization, invite collaborators, and assign the least privileged organization role. Use the organization as the owner for registries, policies, tokens, notifications, and release evidence that must survive individual account changes.
4. Complete a first scan
Follow complete your first governed scan to configure a registry or choose another scan source, inspect the result, and validate a policy verdict before connecting CI/CD.
5. Connect automation
Create a scoped organization token, run the CLI in a non-blocking pipeline first, and then add policy rules and a CI/CD gate once the scan and recovery behavior are understood.