---
title: Explore Signals and support in the dashboard
sidebar_label: Signals and support
description: See how the dashboard reads project Signals status and alerts through Ovok and keeps the screen read-only.
---

# Explore Signals and support

The dashboard's Signals page is a read-only view for a connected project. It does not configure enrollment, change thresholds, or acknowledge alerts, and it does not call the Signals service directly.

## Trace the request

When the practitioner is in sandbox mode and opens **Signals setup**, [`src/App.tsx`](https://github.com/Ovok-Dev/rpm-web-dashboard/blob/main/src/App.tsx) requests project settings and a limited list of unacknowledged raw alerts through the existing `OvokClient`. It tracks each result independently so one failed request does not erase a successful result from the other request.

[`src/components/SignalsPage.tsx`](https://github.com/Ovok-Dev/rpm-web-dashboard/blob/main/src/components/SignalsPage.tsx) renders the returned status, alert list, loading and error states, and a read-only indicator. The source links and UI point administrators to the current Ovok setup and [Signals authorization guidance](/access-policies/signals).

## Support links

[`src/components/SupportPage.tsx`](https://github.com/Ovok-Dev/rpm-web-dashboard/blob/main/src/components/SupportPage.tsx) is a small navigation surface for documentation and companion-device instructions. Device pairing remains in the patient mobile app.

For the platform contract, see [Signals](/signals) and [Working with Signals as a connected part of Ovok](/signals/connected-ovok).