Organization
Your Vulnesis organisation, the people and service accounts in it, the secrets vault, integrations, messaging and notifications, and which page handles each.
These pages are for the owners and admins who set up and run a Vulnesis organisation: who is in it, which credentials CI uses, where provider keys and integration secrets are kept, and where alerts are sent. Read them before you connect a product, because every product’s data and policy belongs to the organisation and takes its credentials from here.
An organisation is the tenant everything else belongs to: scan data, policies, vault entries, connections and members. It is created by the first person to sign up with a company domain, or as a personal organisation for a free-mail address.
The parts
| Part | Resolve Platform page | Read |
|---|---|---|
| Members, roles, invitations and access requests | Account › Members (/resolve/members) |
Members and roles |
| API keys, service accounts for CI, Business key seats | Account › Members, Account › Profile | Service accounts and API keys |
| Secrets vault: AI provider keys, sandbox variables, integration credentials | Configuration › Secrets Vault (/resolve/vault) |
Secrets vault |
| GitHub App, other forges, chat providers, cloud and registry connections | Configuration › Integrations (/resolve/integrations) |
Integrations |
| What is sent where: connections, routes, templates, delivery | Configuration › Messaging (/resolve/messaging) |
Messaging, Signed webhooks |
| Browser and phone push, preferences, quiet hours | Settings › Notifications | Notifications |
| API usage, Pix Sandbox and Pix calls, AI Firewall and Package Firewall decisions, reviews | Account › Logs (/resolve/logs) |
Logs |
| Proxies, TLS interception, allowlists | Corporate proxy |
In this section
- Quickstart: set up a new organisation step by step.
- Plans and add-ons: the plans, the Package Firewall and SOC Intelligence add-ons, invoices and usage.
- HTTP API: every organisation, vault, integration, messaging and notification route, with the credential it takes.
Two kinds of credential
| Credential | Header | Works on |
|---|---|---|
| Resolve Platform session (Authentik sign-in) | vdb_token cookie or Authorization: Bearer <JWT> |
everything |
| API key of a person or service account | Authorization: ApiKey <principalUuid>:<apiKey> |
scan data, findings, policies, campaigns, the CLI. Not members, service accounts, key seats, the vault, integrations, messaging or notification settings. |
Plans
| Feature | Plan |
|---|---|
| Members, roles, invitations, service accounts, the vault | every plan |
| Business API key seats | Business and above |
| Chat and issue delivery, messaging routes | Pro and above |
| Cloud and SaaS integrations, registry logins | Pro and above |
A gated route answers 200 with planLocked: true rather than 403.
Audit
Sensitive changes (invitations, role changes, removals, password and MFA resets, API key views and rotations, service accounts, vault changes) emit security.* and vault.* events. They are recorded even with no route, kept 180 days, and visible to owners in Messaging › Activity. Route them to a channel to be told as they happen; see Messaging.
Platform IaC
The organization’s own settings are kinds: Organization, Member, ServiceAccount and NotificationDefaults for the organization and its people; VaultEntry for its secrets; GitHubInstallation, ForgeConnection, MessagingConnection, MessagingRoute, MessagingTemplate and WizConnection for its integrations. The config engine applies them, and Terraform and OpenTofu manages them. An owner or a developer can apply Organization, Member, ServiceAccount and VaultEntry as code; a developer grants up to developer and cannot change an owner. In the Resolve Platform only an owner manages them. A new Member reports Pending until the invitation is accepted, and a ServiceAccount’s key is shown once, in the apply that creates it; see status phases.
Drift protection
Drift protection is the organisation setting that decides what the Resolve Platform does with settings that Terraform or a GitOps repository manages. Off, the default, the Resolve Platform marks them as managed and still lets you edit them, and the next apply may overwrite your change. On, the server refuses console and legacy API changes to them with HTTP 409 managed_by_platform_iac, and the Resolve Platform shows the page read only. Pages with nothing managed as code are never affected.
- Where it is. The Platform IaC indicator in the top-right of a Resolve Platform page, beside the ? icon (alone where the page has no ?), opens a menu with the switch. The same switch, with an explanation, is on Account › Profile (
/resolve/account), in the card Platform IaC drift protection. - Who can switch it. An organisation owner or admin, at any time. Other members see the state and the text
Only an organisation owner or admin can switch Drift protection. - Everything else (the three states, what read only means, the limits) is on Drift protection.