Product guide · English
Set policy and exceptions
Manage versioned organization policy, use dated exceptions for specific accepted risks, and inspect how a repository policy changes the effective gate.
Steps
- As an owner or admin, open Workspace settings → Organization → Policy. Review the form or YAML for finding limits, secret handling, licenses, advisories and required checks.
- Save with a meaningful note. Each save creates a version; restoring from History creates another version rather than rewriting previous decisions.
- For a scoped waiver, request an exception with its target, reason and expiry. Members can request; an admin approves, rejects or revokes. Check active status before relying on it.
- If using vetkit.policy.yaml in a repository, inspect the effective policy and any ignored settings in the PR result. Repository files can only tighten the organization policy unless an admin explicitly permits loosening.
Read the result
Policy controls gates; an exception records accepted risk and is not a remediation. Past PR reviews retain their pinned policy evidence. An invalid repository file falls back to organization policy and fails the PR check with an explanation.
Limits and availability
An exception cannot turn incomplete evidence into a complete result. Repository-file exceptions are subject to the loosening setting. A date-only expiresAt ends at 00:00 UTC on that date, so choose the intended expiry carefully. Required-check enforcement still belongs to the source repository configuration.
This guide describes the implemented workflow. The features available in your workspace depend on account capabilities and configuration; advanced workflows are not all included in Free Quick Scan. Check the available controls and the evidence returned by each run.