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 its own threshold on its edit form.

Open Notifications → Quiet hours (owner or admin to change it; every member can see it).

Setting the window

Turn it on 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.

What it does, and doesn’t, hold back

• Held, not lost. A notice 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.

Next

• Silences and mutes — hold back specific incidents or one source, on your own schedule
• Routing rules — where each destination’s quiet-hours threshold is set