> 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/monitors/dr.-sprinto-and-manual-inputs.md).

# Dr. Sprinto & Manual Inputs

Dr. Sprinto is Sprinto’s lightweight agent used to collect local system data that cannot be fetched through cloud integrations alone. It enables monitoring of critical controls on employee endpoints, such as screen lock enforcement, OS updates, device health, and auto logout policies.

In addition to Dr. Sprinto, Sprinto supports manual evidence uploads and manual workflows for controls that are not automatable — allowing flexibility in satisfying compliance requirements across varied environments.

This article outlines what Dr. Sprinto captures, when to use manual inputs, and how both methods help resolve monitors.

***

### What is Dr. Sprinto?

**Dr. Sprinto** is a device-level agent that runs locally on user systems (Windows/macOS). It allows Sprinto to:

* Detect screen lock and auto-lock configurations
* Track OS patch status (up-to-date or outdated)
* Report last activity and device compliance status
* Help complete device-specific workflow checks

{% hint style="info" %}

#### Note

* Dr. Sprinto is **non-invasive** and does not collect personal files, browsing activity, or keystrokes.
* DrSprinto is supported only on physical devices such as laptops and desktops. It does not work on virtual machines (VMs), and data from such environments will not be captured or reflected in Sprinto.
  {% endhint %}

***

### Common Monitors Resolved by Dr. Sprinto

<table><thead><tr><th width="321.73828125">Check</th><th width="296.3046875">Resolution Type</th></tr></thead><tbody><tr><td>Auto screen-lock on Windows/macOS</td><td>Automatic via Dr. Sprinto</td></tr><tr><td>Device OS should be up to date</td><td>Automatic via Dr. Sprinto</td></tr><tr><td>Manual device health reporting</td><td>Optional via Portal</td></tr><tr><td>Windows Registry Policy Compliance</td><td>Requires manual file or screenshot</td></tr><tr><td>Powershell-based checks</td><td>Requires manual export or input</td></tr></tbody></table>

***

### Installing Dr. Sprinto

1. Admin generates download links from **Settings → Dr. Sprinto Agent**
2. End-users download and install the agent
3. Once active, Dr. Sprinto will:
   * Auto-sync with Sprinto every few hours
   * Send encrypted compliance signals from the device
   * Display device status in the **Monitoring > Devices** tab

***

### Video Guide

Here's a short video on how to report a device via Dr. Sprinto.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FKSG5OEpFS5gGmbYnuQnb%2FHow%20to%20report%20your%20device%20using%20Dr.%20Sprinto_.mp4?alt=media&token=8ae33bcd-af36-47b9-a97e-b513fdd1b71b>" %}

***

### Manual Inputs via Employee Portal

In cases where:

* Dr. Sprinto is not installed
* The endpoint is BYOD or out of Sprinto scope
* The control requires human confirmation (e.g., shared account lock policy)

Sprinto allows end users to submit compliance evidence manually.

Steps:

1. Navigate to the **Employee Portal**
2. Select the required task (e.g., Report screen-lock, confirm antivirus)
3. Submit form responses, screenshots, or mark as completed
4. Admins can review these submissions in the Monitoring tab

{% hint style="info" %}
If a device is not manually reported on a daily basis, its validity is retained in Sprinto for up to **90 days** from the last reported update. After that, the device is considered unmonitored.
{% endhint %}

***

### Manually Resolving Device-Specific Checks

If Dr. Sprinto cannot fetch certain signals (e.g., registry-level policy settings), use:

* Windows PowerShell exports
* Registry screenshots (`regedit`)
* Policy summary reports
* Annotated screenshots from Settings or Group Policy Editor

Submit these via **Upload Evidence** against the failing check.


---

# 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/monitors/dr.-sprinto-and-manual-inputs.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.