How the System Works
What triggers a notification
Every event that produces a notification, who receives it, and which ones you can turn off.
This page is a placeholder. Its structure is fixed; the writing lands in a later phase.
Every notification comes from an event below. Only three can be switched off.
What sends one
| Event | Who hears it | Off switch |
|---|---|---|
| A float, and its reminders | You | No |
| A swap or handoff, and its outcome | The other party | No |
| Your shift dropped or cancelled | You | No |
| A schedule published | Everyone assigned | No |
| Preference windows and break sign-up | Workers | No |
| A seat opening at your house | Everyone eligible but you | No |
| A seat opening at another house | Workers eligible there | Opt in |
| A seat still uncovered 3 hours out | Same workers | On for your house |
| Your own shift starting soon | You | 2h, 1h, or 30m |
| Nobody left to float | One manager, by ladder | No |
Eligible means active student workers, student managers, and housing managers, never a building manager. Only Harnwell workers hear about a Harnwell seat, because nobody else may staff that desk. A locked seat is never announced, because nobody can claim it.
Why it works this way
A notification is optional only when ignoring it costs nothing. A float, a swap, and a published schedule each need an answer from one person, so none carries a switch. A shift reminder asks nothing back, so you pick lead times or none. Settings still list the mandatory channels, on and disabled, so you can see that a swap request always reaches you.
What this means for you
Never open settings and you get the defaults: an hour’s warning before each shift, and your own house only. Other houses stay silent.
Managers get no push. An Allied request reaches them as a console alert, so silence there means every desk is accounted for.