Sign in
Super admin only.
Fleet is polled every 60 seconds. Suspended stations aren't polled.
Support
Questions and tickets from stations. Answering one well is the documentation - the studio's assistant quotes answered threads when somebody asks the same thing again.
Who tickets can be given to
Names, comma separated. This is "whose job is this", not a login.
staircaseradio.co
How people find the sales site, from our own Google account.
Platform settings
Set once here, used by every station. Nothing to edit on any server.
Google (Search Console & Analytics)
From the Staircase Radio project in Google Cloud - Google Auth Platform > Clients. Stations use it to connect their own Google account and see their search figures in the studio.
Sales blog
The stories on staircaseradio.co/blog. Saving publishes instantly - no deploy needed.
Edit post
**double stars** make text bold. Lists: one item per line.
Releases
Publishing a release tells every station a studio update is ready. Their admins read your notes and choose when to install - now or scheduled. The HQ Update buttons still work as a force-update.
From the stations
Everything the stations have sent up: bugs their admins judged real, and feature ideas with their DJs' votes. Fix bugs, tick them, release once - the station's studio shows every status change within a minute.
Release these fixes
They all go onto the same release. Every station's admin gets an Update button; the DJs who reported them are told once their station updates.
How it works
The whole loop in one line: stations report, you fix, you push code, you publish a release, stations press Update. Everything in the sidebar is one part of that.
- The fix or feature is built and the code is pushed. Nothing has reached any station yet.
- Fleet → Update on your TEST station (Sunset Sounds) - a force-update installs the newest code on that one station only, silently. No release, no notes, nobody else sees anything.
- Test it there. Actually try the thing that was broken.
- Happy? Announce it: tick the fixed bugs on From the stations and press Release the ticked fixes - or, for changes with no bug behind them, write the notes on Releases and press Publish. This is the moment the fleet hears about it.
- Every station's admin now sees an Update button with your notes, and installs when it suits their schedule. DJs who reported a fixed bug are told automatically once their station takes it.
The order matters: publish the release BEFORE force-updating a station you want prompted - a station already on the newest code has nothing to install, so it never sees the button (the notes still show on its What's new page). And the Update buttons warn you if anyone on that station is live or mid-take.
Every station, its version and its health. The Update button HERE force-updates a station right now, without asking them - use it for your own stations or an emergency. Normally stations update themselves.
One board for everything sent up: bugs their admins judged real, and feature ideas with their DJs' votes. Filter by type, and by where it stands - Needs a look, In hand, Settled. For a bug: New means nobody here has looked, Working tells the station it is in hand and shows them your ETA, Declined says it will not be fixed, with your note as the reason. For a request: set considering, planned, building, done or declined and their studio shows it within a minute. When fixes are pushed: tick the bugs, press Release the ticked fixes, write the notes once - that publishes the release for you.
Publishing tells every station an update is ready: their admin reads your notes and presses Update when it suits them. This is also the door for changes with NO bug report behind them - push the code, write what changed, publish. One release per pushed version: if the version is already published, the new notes go on that release via the Bugs panel, or push new code first.
A message straight to the notification bell of every staff member at the stations you tick - maintenance windows, planned downtime, anything they should hear from you before they notice it themselves. Nothing to install, nothing tracked beyond whether an admin opened it.
The Community forum and station tickets. Questions answered here teach every studio's assistant; tickets carry a team member's name. Different from Bugs: Support is "how do I", Bugs is "it is broken".
A station that is already ON the newest code sees no Update button - there is nothing for it to install. Force-updating a station from Fleet and THEN publishing the release means that station skips the prompt entirely; the notes still show on its What's new page. Publish first, update second, and the flow reads properly.
Wording
Every word on a studio screen. Change one here and it changes at every station within 3 minutes. Nothing is copied to a station until you save it.
The studio assistant learned the code's wording, so a renamed button leaves it naming the old one.
Station notices
Lands in every staff member's studio notification bell at the chosen stations. A notice counts as read once one of that station's admins has opened it.