# After your first screen


> The five things worth doing once one screen works, in the order that saves the most rework later.
[Get started](/docs/get-started/) takes you to one screen playing content. This is what to do next, in the order that costs least to change now and most to change later.

## 1. Settle a naming convention

Before the second screen, not after the twentieth.

Name for where a screen is, not what it shows. What it shows changes; where it is does not. Give names a shared shape, such as `Site, room, position`, and searching for a site then lists everything in it.

Renaming later is possible but tedious, and half-renamed fleets are worse than consistently badly named ones. See [Name, location, and notes](/docs/screens/setup/name-location-and-notes/).

## 2. Set up labels before you need them

With one screen, assigning a playlist directly is fine. At five it is annoying, and at fifty it is the main thing standing between you and a content change.

Label by facts that do not change: `frankfurt`, `plant-floor`, `reception`, `24h`. A screen carries several, so you get the combinations free without inventing `frankfurt-reception`.

Resist campaign labels. `summer-promo` needs removing from twenty screens in September, and it never gets removed. Put the campaign in the playlist's schedule and let it expire on its own. See [Labels](/docs/labels/).

## 3. Turn on alerts that reach someone

An offline screen keeps playing cached content, so nothing looks wrong until it does. Email alerts are on by default and go to workspace members; Slack and PagerDuty are worth wiring up if a dark screen is somebody's job.

Send them somewhere of their own rather than into a busy channel. See [Alerts](/docs/screens/monitoring/alerts/).

## 4. Invite members, and set the owner correctly

Everyone in a workspace sees everything in it, so decide early whether one workspace covers your whole organization or whether teams need their own.

Transferring ownership takes a minute while the owner is still here. Recovering a workspace whose owner has left and whose mailbox is closed takes days. See [Roles and permissions](/docs/workspaces/people/roles-and-permissions/).

## 5. Check the screen from the dashboard, not the room

Once a screen is working, confirm you can tell it is working without walking to it: a screenshot on its Overview tab, a clean Details tab, and the right content on Now playing.

If you cannot answer "is it fine?" from the browser, the fleet does not scale past the screens you can see from your desk. See [Monitoring](/docs/screens/monitoring/).

## Then, when you need it

Live data on a screen means an [app](/docs/apps/) or an [integration](/docs/integrations/). Content behind a login means [authenticated pages](/docs/content/web-pages/authenticated-pages/). Doing any of this in bulk means the [API](/docs/developers/).