# Dashboard requirements


> The browser the dashboard runs in, the hostnames it has to reach on a restricted network, and the two things that most often break it.

This page is about the browser you manage screens from. What the screens themselves need is a separate list, in [Hostnames and ports](/docs/it-requirements/reference/hostnames-and-ports/).

## The browser

The dashboard is a JavaScript application and runs in any current version of Chrome, Edge, Safari, or Firefox. There is nothing to install and no plugin.

There is no non-JavaScript version. A browser or a corporate policy that blocks scripts blocks the dashboard entirely.

## Ad blockers break it

This is the single most common cause of a dashboard that half works: sections render blank, or buttons that should be there are missing.

The fix is to disable ad blockers for the dashboard and restart the browser. If a page looks broken in a way that seems too strange to be a real bug, check this before reporting it.

## Hosts the dashboard needs

On a restricted corporate network, allow these outbound over HTTPS on 443.

| Hostname | Why |
| --- | --- |
| `login.screenlyapp.com` | The dashboard itself, and signing in |
| `api.screenlyapp.com` | The API behind every page |
| `ws.screenlyapp.com` | Live connection, for status that updates without a refresh |
| `us-assets.screenlyapp.com` | Screenshots, thumbnails, and content you upload |

> [!IMPORTANT]
> Allow the hostnames, not resolved IP addresses. We use Cloudflare in front of our infrastructure and the addresses change.

## Hosts that only affect the edges

Blocking these does not stop you working. The parts that use them go quiet.

| Hostname | What stops |
| --- | --- |
| `www.youtube.com` and Google's APIs | The video feed on the Home page |
| `screenly.io` | The product news feed on the Home page |
| `support.screenly.io` | The Help Center link |
| `shop.screenly.io` | Hardware links |
| Sentry, and Google reCAPTCHA | Error reporting, and a check on the sign-in form |

If Home looks emptier than the screenshots in these docs, this list is usually why, and nothing is actually wrong.

## Passkeys need a current browser

Signing in with a [passkey](/docs/account/signing-in/ways-to-sign-in/) uses WebAuthn, which every current Chrome, Safari, Edge, and Firefox supports. On an older browser the passkey option will not appear, and a one-time email code still works.