Quiet hours
One window, for the whole workspace. During it, a notice below a destination’s own quiet-hours threshold is held back — each destination sets what still gets through.
Quiet hours live on Notifications → Muting, beside silences and source mutes (owner or admin to change them; every member can see them).
Setting the window
Section titled “Setting the window”The Quiet hours card shows the window in its title — on, 23:00–07:00, or off (23:00–07:00 when on) — so you see it without opening anything. Turn on Enable quiet hours and set a From and To time, in the workspace’s own time zone. A window that runs past midnight (23:00 to 07:00, say) is fine — it’s read as one night. While it’s on, Messages held back then won’t be delivered later stays visible beside the switch; the rest of what quiet hours don’t cover (corrections, Do Not Disturb, daylight saving) sits folded underneath.
What still gets through, per destination
Section titled “What still gets through, per destination”Under the window, one sentence says what quiet hours do, from each destination’s threshold — for example “When on, 23:00–07:00: Phones get Critical only; Telegram gets everything.” A destination set to Everything isn’t quieted at all.
Below it, every destination has a Still gets through picker: Critical only (the default), Error and above, and so on down to Everything. The sentence follows your picks before you save. The destination’s own edit page has the same setting.
The switch, the window and the pickers save together through one save bar: Save confirms with Saved and an Undo that puts all of it back.
What it does, and doesn’t, hold back
Section titled “What it does, and doesn’t, hold back”- Held, not replayed. A message held by quiet hours isn’t sent late once the window ends — the inbox already has it, and nothing arrives after the fact to surprise you in the morning.
- A destination’s own threshold decides who still hears what. Set a phone’s threshold to CRITICAL and a Slack channel’s to WARNING, and the phone stays quiet for things the channel still posts.
- Recoveries and corrections still go through, silently. If a destination was already told about an incident, quiet hours never leave it looking wrong — a resolve or a state correction for that incident still updates it, just without a sound.
- A test always goes through. Sending a test from a source or a destination bypasses quiet hours entirely, on purpose — it exists to prove the destination itself works.
- Your phone’s own Do Not Disturb or Focus mode still applies on top. Quiet hours can’t override those; they only decide what InfraInbox itself sends.
- Daylight saving isn’t special-cased. The window is wall-clock time, so a night that crosses a clock change runs an hour shorter or longer, like any other alarm set by wall-clock time.
- Silences and mutes — hold back specific incidents or one source, on your own schedule
- Routing — which destinations an event reaches in the first place