> 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/staff-devices/dashboard-actions/report-device-status-via-employee-portal.md).

# Report Device Status via Employee Portal

If Sprinto is unable to automatically fetch a staff member’s device health status—due to OS compatibility issues, Dr. Sprinto app errors, or unsupported configurations—employees can manually report their device status via the Sprinto Employee Portal.

This article explains how staff members can upload their device configuration evidence manually to meet compliance requirements.

***

### Before You Begin

Ensure that:

* **Dr. Sprinto** is already configured as the MDM tool on your Sprinto account.
* The **Dr. Sprinto app** is installed on your device (optional but recommended).
* You are logged in to the Sprinto Employee Portal.

***

### Step 1: Access the reporting interface

1. Log in to the **Sprinto Employee Portal**.
2. Click **Your Devices** from the main dashboard.
3. Click **Report Device**.

<figure><img src="/files/3DiRLKYQF0JY5DlSKKxT" alt="" width="563"><figcaption></figcaption></figure>

***

### Step 2: Attempt to fetch device data

1. Click **Add a new device**.
2. Click **Fetch** to allow the Dr. Sprinto app to automatically collect and upload your device health data.
3. If the fetch is successful, you will see a success message and no further action is required.

<figure><img src="/files/JhdQomnryM3ROoCn5ZX7" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}
&#x20;If the fetch fails (due to app issues, permissions, or OS mismatches), proceed to upload the evidence manually.
{% endhint %}

***

### Step 3: Upload evidence manually

1. Click **Upload Evidence**.
2. Enter the following details:
   * **Device name**
   * **Serial number**
   * **Operating system** (choose from dropdown)
3. For each required device check (e.g. OS version, screen lock, disk encryption):
   * Click **Upload Evidence** next to the check.
   * Attach a screenshot or system document showing the configuration.
   * Click **Upload** to confirm.

{% hint style="info" %}
Only files that clearly show the required system setting should be uploaded. Refer to your company’s compliance checklist for specifics.
{% endhint %}

***

### Step 4: Submit the report

1. Select the **device ownership**:
   * **Company** – If the device belongs to the organisation.
   * **Employee** – If the device is personal but used for work purposes.
2. Click **Submit Report**.

Once submitted, the device status will be visible on the **Your Devices** page and available for admin review.

***

### What You Can Do

* Re-upload evidence if your previous submission was rejected.
* Monitor failing or pending checks in your device view.
* Reach out to your admin if you’re unsure which checks are required.


---

# 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/staff-devices/dashboard-actions/report-device-status-via-employee-portal.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.
