Docs

Policies

A policy defines the conditions that must be met for a change request to be merged. Each policy defines one or more rules which assert these conditions. All rules must be met for the policy to be satisfied.

A policy with no enabled rules will always be unsatisfied. Similarly, a rule is unsatisfiable if the number of eligible reviewers is fewer than the required minimum reviews.

Fields

Name

The name by which the policy is referenced.

Default Policy

If enabled, this policy will be automatically pre-selected when creating new change requests via the web UI. Only one policy may be designated as the default at a time.

The default policy applies only to the web UI. API consumers must always specify a policy explicitly when creating change requests.

Require Independent Review

If enabled, a change request owner's own reviews will not count toward satisfying any of this policy's rules. This enforces separation of duties: someone other than the owner must approve the change before it can be merged.

The owner may still submit reviews on their own change request (for example, to respond to feedback or add context), and those reviews still appear in the review list. They are simply excluded when counting approvals against the policy's rules.

This setting is per-policy, so different policies can carry different requirements (for example, a low-risk policy might allow self-review while a critical-change policy requires independence). The default is disabled, which preserves the prior behavior of counting the owner's reviews like any other reviewer's.

If the owner is the only eligible reviewer for a rule under independent review, that rule cannot be satisfied for their change requests. Add another eligible reviewer to the rule.

Description

A brief description of the policy's purpose.

Comments

Free-form text for additional context or notes about the policy.

Tags

Policies support NetBox's tagging and custom fields features.

On this page