> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/data-library/vulnerabilities/dashboard-actions/create-and-manage-workflow-checks.md).

# Create and Manage Workflow Checks

Workflow checks help you stay compliant with security frameworks when vulnerabilities cannot be automatically tracked through integrations. These checks act as manual reminders to perform regular actions—such as running scans, reviewing code, or verifying third-party libraries—and require evidence submission to be marked as complete.

You can use either predefined checks available in Sprinto or create your own custom checks.

***

### Before You Begin

Ensure that:

* You are logged in as an administrator.
* Your vulnerability monitoring source is not integrated, or you need to track additional compliance actions manually.
* You have identified which controls or processes require periodic verification.

***

### Procedure

#### 1. Add a Workflow Check

1. Go to **Data Library > Vulnerabilities > Overview**.
2. Click **+ Add workflow check**.
3. In the pop-up, select a predefined check or click **Create your own check**.
4. Fill in the check details:

| Field            | Description                                                        |
| ---------------- | ------------------------------------------------------------------ |
| **Title**        | Name of the workflow check                                         |
| **Description**  | Purpose of the check and why it’s required                         |
| **Instructions** | Steps to perform the check and what evidence to attach             |
| **Area**         | Compliance framework or control ID related to the check            |
| **Activates on** | Date from which the check should be active                         |
| **Runs on**      | Frequency of recurrence (e.g. monthly, quarterly)                  |
| **Assigned to**  | Person responsible for performing the check and uploading evidence |

5. Click **Add Check** to save and activate the workflow check.

***

#### 2. Edit a Workflow Check

1. Navigate to **Vulnerabilities > Workflow Checks**.
2. Click the workflow check you want to update.
3. Click **Edit** to modify fields like instructions, frequency, or assignee.
4. Click **Enable Check** to save the changes.

> Note: Edited checks retain their previous history but reflect new instructions from the next scheduled run.

***

#### 3. Disable a Workflow Check

1. Locate the check under the **Active** tab.
2. Click the options icon (⋯) and select **Disable Check**.
3. The check is removed from active tracking and appears under the **Inactive** tab.

You can re-enable it later if needed.

***

### Result

The workflow check appears in the list with its assigned frequency and status (e.g. *Due*, *Critical*, *Passing*). Assigned stakeholders will be notified to run the check and upload evidence per the compliance schedule.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sprinto.com/data-library/vulnerabilities/dashboard-actions/create-and-manage-workflow-checks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.