> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cysmiq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Snoozes

> Temporarily pause vulnerability and policy violation follow-up with governed approvals, limits, and scoped settings.

## Overview

Snoozes temporarily pause follow-up on vulnerabilities and policy violations for a fixed duration. Use snoozes when the item remains valid, but the team needs time for remediation, an upstream fix, or a planned review window.

Snoozes keep the item visible in Cysmiq while recording who requested the pause, how long it should last, and whether approval was required.

When a vulnerability is snoozed, related open or pending-review policy violations for that vulnerability are snoozed for the same window.

<Info>Availability depends on your Cysmiq plan.</Info>

After snoozes are enabled:

* **Snoozes** appears in the workspace navigation
* Workspace owners can configure governance from **Snoozes**
* Vulnerability and policy violation action menus include **Snooze**

## Governance settings

The **Snoozes** settings page has separate governance sections for **Policy violations** and **Vulnerabilities**.

Each section supports the same settings:

| Setting              | Meaning                                                                                                            |
| -------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Require approval** | If enabled, snooze requests stay pending until an approver approves them. If disabled, requests apply immediately. |
| **Max snoozes**      | Maximum approved snoozes allowed for each item. A value of `0` means no limit.                                     |
| **Approver roles**   | Roles that can approve, reject, or clear snoozes for the selected scope.                                           |

Default settings:

| Target            | Require approval | Max snoozes | Approver roles |
| ----------------- | ---------------- | ----------- | -------------- |
| Policy violations | Enabled          | 2           | Owner          |
| Vulnerabilities   | Enabled          | No limit    | Owner          |

## Scope overrides

Snooze governance can be configured at these scopes:

* **Workspace**
* **Organization**
* **Repository**
* **Application**

Selected scopes inherit effective settings from broader scopes until an override is saved. Use **Reset overrides** to clear local settings and return the selected scope to inherited behavior.

## Request workflow

Users request snoozes from the **Snooze** action on a vulnerability or policy violation.

The request form includes:

| Field        | Values                                            |
| ------------ | ------------------------------------------------- |
| **Duration** | 1 day, 3 days, 7 days, 14 days, or 30 days        |
| **Reason**   | Optional text describing why the snooze is needed |

After the user selects **Request snooze**, Cysmiq either applies the snooze immediately or creates a pending request based on the effective **Require approval** setting.

## Review workflow

Pending requests show who requested the snooze and the requested duration.

Available actions depend on the user's role and relationship to the request:

| State                             | Available actions       |
| --------------------------------- | ----------------------- |
| Pending request for an approver   | **Approve**, **Reject** |
| Pending request for the requester | **Cancel request**      |
| Pending request for other users   | **Awaiting approval**   |
| Active snooze for an approver     | **Clear snooze**        |

Approving a request applies the snooze and increments the item's snooze count. Rejecting or canceling a pending request leaves the item active.

Clearing an active snooze ends the current snooze window.

## Related docs

* [Vulnerability detail view](/vulnerability-management/vulnerability-detail-view)
* [Policy violations](/policies/violations)
* [Vulnerability lifecycle](/vulnerability-management/lifecycle)