> For the complete documentation index, see [llms.txt](https://docs.nullify.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nullify.ai/configuration/configuration-general.md).

# General Configuration

## Overview

After installation, repository enrollment, and any required onboarding approval, Nullify can assess pull requests and create findings for new risks. The defaults get most teams moving quickly, and you tailor behaviour from the Nullify dashboard (with an equivalent admin API for automation). Configuration no longer lives in a checked-in file — every setting is managed centrally per tenant.

## Where settings live

| Setting                                                       | Dashboard                                                             | API                                                                             |
| ------------------------------------------------------------- | --------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
| Automatic scans, CI / PR gate (fail build, enable PR reviews) | **Settings → Repository scans**; legacy **Configure → Pull Requests** | `PUT /admin/pr-gate-settings`                                                   |
| Ticket creation thresholds (per finding type)                 | **Settings → Ticketing**                                              | `POST /admin/ticketing/settings/{findingType}`                                  |
| SLA policies                                                  | **Settings → Ways of working → SLA & effort**, where enabled          | `PUT /admin/sla/bulk`, `POST /admin/sla`                                        |
| Notification destinations + event filters                     | **Settings → Connectors**, where offered                              | `PUT /admin/integrations/notifications`                                         |
| Ignore / allowlist a finding                                  | Per-finding in the dashboard                                          | `POST /{service}/.../findings/{findingId}/allowlist`                            |
| Repositories and directories scanned                          | **Settings → Connectors → Scan scope**                                | `PUT /admin/scan-scope`, `PUT /admin/repositories/scan-scope`                   |
| Workspace capability switches                                 | **Settings → General → Capabilities**                                 | `GET /admin/tenant-capabilities`, `PUT /admin/tenant-capabilities/{capability}` |

### Scan scope

**Settings → Connectors → Scan scope** chooses which repositories Nullify scans for code (code, dependencies, containers and supply chain) and for secrets (credentials and sensitive data), and which directories of each it includes or excludes. Repositories newly brought into scope get a default-branch scan. Changing scope needs the `config:write` permission; limits Nullify sets for your workspace show read-only. See [Scan scope](https://docs.nullify.ai/api-reference/api-reference/api-admin/repositories-and-code.md#scan-scope) for the API.

### Capabilities

**Settings → General → Capabilities** lists workspace switches you can turn on or off, or hand back to the Nullify default: **Webhook processing**, **Git platform writes** (off keeps Nullify read-only: no check runs, statuses, comments, reviews, branches or pull requests, while scans still run and results stay on the dashboard), **Scheduled dependency scans**, **Scheduled cloud scans**, **Cloud and supply-chain fixes**, **Fix pull request reviewer messages**, **Additional review reminders**, **Merge-ready reminders** and **Threat investigation shared-channel messages**. Nullify can lock a switch, for example while onboarding is in progress; the page then shows the reason. Changes need the `config:write` permission.

### Pull request gate

Control whether Nullify scans pull requests and pushes automatically, whether the Nullify check can fail CI when a pull request introduces a new finding, the priority threshold that fails it, and how Nullify reviews. Use **Settings → Repository scans**, legacy **Configure → Pull Requests**, or the settings API (`PUT /admin/pr-gate-settings`).

Main `PUT /admin/pr-gate-settings` fields:

* `prScansEnabled`, `pushScansEnabled` — automatic pull request and push scans (on by default).
* `findingsPolicy` — `confirmed` fails the Nullify check when the PR introduces an AI-confirmed finding at or above the threshold; `none` (the default) never does. The legacy `enabled` field must agree with it.
* `cvssEnforcement`, `scaBlockCvssThreshold` — fail on a new dependency or container CVE at or above a CVSS cutoff (default 9.0), without AI triage.
* `secretsEnforcement` — fail on a new credential triaged Low priority or above.
* `minPriority` — the lowest priority that fails the check. Accepts `URGENT` or `IMPORTANT` only.
* `prReviewsEnabled` — whether Nullify reviews pull requests (on by default).
* `allowRequestChangesReviews` — allow Nullify to submit a request-changes review when it has a blocking security concern (off by default).
* `allowApprovingReviews` — API only: allow Nullify to submit an approving review on a pull request that has no blocking findings (off by default).

See [Repository Scans](https://docs.nullify.ai/configuration/configuration-pull-requests.md) for the full behaviour of each setting.

### Ticketing thresholds and SLAs

Ticket auto-creation is **off by default** for every finding type until you enable it per type from **Settings → Ticketing** (`POST /admin/ticketing/settings/{findingType}`). Once enabled, a ticket is created when a finding meets both the configured severity and priority thresholds.

Default thresholds once enabled:

* Priority default: **IMPORTANT** (and Nullify never auto-creates tickets below IMPORTANT, regardless of the threshold).
* Severity default: no floor.

SLA policies (time-to-remediate targets per priority) are set with `POST /admin/sla`. Valid priority labels for that operation are `URGENT`, `IMPORTANT`, `MEDIUM`, and `LOW`. The dashboard grid edits **Urgent**, **Important** and **Negligible** through `PUT /admin/sla/bulk`; see [Remediation SLAs](https://docs.nullify.ai/configuration/configuration-ticketing.md#remediation-slas).

### Notifications

Notification destinations and the events that trigger them are managed from connector settings where available, or through the API (`PUT /admin/integrations/notifications`). Nullify supports three destination types, each pairable with an event filter:

* **Slack** — send supported events to configured channels. Microsoft Teams conversations and escalations use their separate integration.
* **Email** — deliver notifications to an address.
* **Outbound webhook** — POST notification events to an HTTPS endpoint you control.

### Allowlisting findings

For finding-level exceptions, use the dashboard or API. Supply-chain policy also supports a coordinate-based package allowlist; see [SCPM settings](https://docs.nullify.ai/api-reference/api-reference/scpm.md). Suppress a finding per-finding from the dashboard or via the service allowlist endpoint, e.g. `POST /sast/findings/{findingId}/allowlist`. See the per-service configuration pages for the exact paths.

## Autofix pull request limits

Manager campaign planning applies these fixed selection limits:

* **3** open Nullify pull requests per repository at a time.
* **5** new pull requests per remediation plan.

These are campaign-plan limits, not a global throttle on ad hoc dashboard, API, or CLI autofix requests.

Issue dashboards are generated automatically from finding counts; there is no toggle to enable them.

## Document ingestion (Vault)

Upload organizational documents from the Documents step of [Onboarding](https://docs.nullify.ai/getting-started/getting-started.md) or with **Add document** on the **Vault** page; both feed the same vault. Files committed to a private configuration repository such as `.github-private` or `.nullify` are not imported.

Useful examples: security architecture diagrams, on-call escalation matrices, GDPR/SOC 2 attestations, vendor risk assessments, incident response runbooks, access review exports. See [Vault](https://docs.nullify.ai/capabilities/context-engine.md#vault) for the file types Nullify reads. Verify the imported documents before relying on that context.

## Detailed configuration guides

* [Ticket routing, SLAs, and fix effort](https://docs.nullify.ai/configuration/configuration-ticketing.md)
* [Notifications and delivery controls](https://docs.nullify.ai/configuration/configuration-notifications.md)
* [Manager autonomy and ground rules](https://docs.nullify.ai/configuration/configuration-manager.md)
* [Cloud accounts and audit lifecycle](https://docs.nullify.ai/configuration/configuration-cloud.md)
* [Account access and teams](https://docs.nullify.ai/configuration/account-and-teams.md)
* [Microsoft Entra SSO, provisioning and recovery](https://docs.nullify.ai/configuration/account-and-teams/entra-sso-and-scim.md)
* [Azure DevOps installation](https://docs.nullify.ai/getting-started/install/azure-install.md)

The current dashboard uses **Settings**; older dashboards use **Configure**. Some controls are API-only. **Settings → Preferences** holds your own dashboard view and appearance; they follow you across devices and do not change the workspace for anyone else. The API field names shown in these guides are JSON names, not database column names.
