# The dashboard


> What the dashboard is, what each item in the navigation does, and which jobs live somewhere other than the browser.
The dashboard is the web app at [login.screenlyapp.com](https://login.screenlyapp.com/). It runs in a browser and needs nothing installed.

It is the only place most people ever touch. Your screens are managed from here whether they run ScreenlyOS on a Screenly player, or Screenly Anywhere on an Android box, a smart display, or a browser. The devices differ; the dashboard does not.

## The navigation

| | |
| --- | --- |
| Home | Where you land. Fleet status at a glance, quick actions for the four things you do most, and product news |
| Screens | Your fleet, their health, their settings, and their labels |
| Playlists | The rotations, each with its own content, schedule, and screens |
| Content | Everything uploaded or added: images, video, audio, PDFs, web pages, streams |
| Apps | Your configured app instances, and the App store you install them from |
| Settings | The workspace: members, integrations, notifications, security, linked workspaces |
| Help Center | Support, in a new tab |

Billing sits apart from that list and is visible only to Owners and Billing Managers.

The four quick actions on Home are add a screen, create a playlist, upload content, and install an app, which is a fair summary of what the dashboard is for.

## What is not done here

**Setting up a device.** Getting hardware or a platform running, and diagnosing one that will not connect, belongs to the device: [ScreenlyOS](/docs/screenlyos/), [Screenly Anywhere](/docs/anywhere/), or [Screenly players](/docs/screenly-players/). Once a screen is paired it is managed from here like any other.

**Anything scripted.** The dashboard is one client of the Screenly API, with no special access. Everything here is available from the API, the CLI, and the MCP server, which is what [Developers](/docs/developers/) covers.

## Who can see what

Access is granted per workspace, and everyone in a workspace sees all of its screens, content, and playlists. What differs by role is who can change people and who can see billing. There are no per-screen permissions.

If some people must not see some screens, that is a separate workspace rather than a role. Worth knowing before you plan around permissions that do not exist. See [Roles and permissions](/docs/workspaces/people/roles-and-permissions/).

## Signing in, and the lobby

There is no password. You sign in with a one-time email code, a passkey, a Google, GitHub, or Microsoft account, or your own identity provider over SAML. See [Signing in](/docs/account/signing-in/ways-to-sign-in/).

If your account belongs to more than one workspace, or you have an invitation waiting, you land on a workspace picker rather than straight in a workspace. It asks you to pick one to continue, and has a second tab for pending invitations where you accept or decline each one. You can also create a new workspace from there.

With exactly one workspace and nothing pending, you skip it entirely, which is why most people never see it.