Give someone a link that opens the schedule filtered to just their shifts. Pick a name, copy the link, and they bookmark it. (Their device also remembers whoever they last picked, so they can just choose their name once instead.)
Colors
Staff and locations now draw from separate, more vibrant palettes (32 staff colors, 12 location colors) so people and stores never look alike and fewer colors repeat.
Existing staff/locations keep the colors you already gave them — use these to refresh them all at once.
Spreads the palette so people listed near each other get very different colors. You can still hand-pick any individual color afterwards in Manage.
Backup & restore (JSON)
Export saves the whole schedule to a .json file on your computer — works even if Power Automate is down (it reads the copy in this browser). Import loads a .json file back in (a backup, or an export). Use it to recover the schedule, or to keep working locally during an outage and sync back when Power Automate returns.
Import replaces the live schedule. During an outage, only one editor should import/edit to avoid diverging copies.
Shared backend — Power Automate (recommended)
Not connected
No app registration and no IT approval needed. Build two Power Automate flows (see the setup guide), then paste their URLs here. The app auto-saves on every change and reloads others' updates every few seconds.
Editors fill in all four boxes below. Viewers get only the Load URL and Read key — leave their Save URL blank and the app opens read-only.
Where do these save? Only in this browser, on this device — not in the file and not shared.
To hand the app to staff so it already has the URLs, build a ready-to-use copy:
Proxy copies (recommended) carry no URLs or keys — they call /api/schedule on their own host and the Cloudflare worker adds the real flow URL + key server-side. The proxy viewer opens read-only, and shows the PIN gate if you've set a viewer code (the code lives in the worker, never in the file). The proxy editor can save; it carries no gate, so protect wherever you host it. Rename either to index.html and deploy it alongside the worker.
The plain viewer / editor copies bake the read / write key into the file in cleartext — only for use without the worker. Treat an editor copy like the write key itself.
