> 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/infrastructure/dashboard-actions/add-and-configure-workflow-checks.md).

# Add and Configure Workflow Checks

### Introduction

In addition to automated system checks, Sprinto supports **workflow checks** that require periodic evidence submissions to validate compliance. These checks are useful when:

* Manual validation is needed (e.g., for backup restoration tests)
* Evidence must be reviewed periodically
* Specific compliance controls are not covered by system integrations

Workflow checks can be applied to both integrated and non-integrated infrastructure systems.

***

### Accessing Workflow Checks

1. Go to **Data Library → Infrastructure**.
2. In the **Infra systems** tab, select a specific system.
3. Click **Add workflow check**.

{% hint style="info" %}
You can also add checks from the **Monitoring → Available checks** tab across all systems.
{% endhint %}

***

### Methods to Add Workflow Checks

| **Method**                             | **When to Use**                                |
| -------------------------------------- | ---------------------------------------------- |
| **From template**                      | Use a prebuilt Sprinto check with default tags |
| **Single workflow check**              | Manually define one check for a system         |
| **Bulk upload**                        | Add multiple checks at once via CSV            |
| *(Coming soon)* Custom check templates | Build reusable check templates                 |

***

### Configure the Workflow Check

After selecting your method, configure the following fields:

<table data-header-hidden><thead><tr><th width="187.79296875"></th><th></th></tr></thead><tbody><tr><td><strong>Field</strong></td><td><strong>Details</strong></td></tr><tr><td><strong>Title</strong></td><td>Name of the check (e.g., “Encryption Enabled on Storage”)</td></tr><tr><td><strong>Description</strong></td><td>Purpose of the check and what it covers</td></tr><tr><td><strong>Instructions</strong></td><td>Steps the assigned user must follow to perform the check and gather evidence</td></tr><tr><td><strong>Check frequency</strong></td><td>How often the check runs (e.g., Monthly, Quarterly)</td></tr><tr><td><strong>Activates on</strong></td><td>When the check becomes active</td></tr><tr><td><strong>Assigned to</strong></td><td>The staff member responsible for running the check</td></tr><tr><td><strong>Evidence review</strong></td><td>Toggle ON to route submissions to a reviewer before passing the check</td></tr></tbody></table>

Once complete, click **Add Check**.

***

### Managing Workflow Checks

Once a workflow check is active:

* It will appear under **Monitoring → Active Checks**
* The assigned owner receives reminder notifications
* Check status is **Due** until evidence is uploaded
* Evidence can include screenshots, PDFs, documents, or shared links
* Reviewers can mark the check as **Passing**, or request rework

***

### Tips

* Use templates to save time when adding common checks like:
  * *Database encryption is enabled*
  * *Disaster recovery is tested*
* Use bulk upload when configuring multiple systems across providers
* Always assign a responsible stakeholder to avoid missed deadlines


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.sprinto.com/data-library/infrastructure/dashboard-actions/add-and-configure-workflow-checks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.