> For the complete documentation index, see [llms.txt](https://help.steeple.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.steeple.com/en/notifications/notifications-plage-horaire.md).

# Time slot — Right to disconnect

The time window feature lets you define one or more slots during which the user **receives** notifications, and outside of which notifications are silent. It is found in the **Settings** of the notification center, section **Notification schedule**.

Only the **push and email channels** are affected: notifications continue to arrive in the notification center, which serves as an archive.

## Configuration

### Enable the time window

Turn on the toggle **Notification schedule** for the window restrictions to apply.

### Define the slots

Each slot has its own days and its own times, entered in this order:

* **Days** : Monday (1), Tuesday (2), Wednesday (3), Thursday (4), Friday (5), Saturday (6), Sunday (7)
* **From** : time at which notifications start being sent (e.g., `09:00`)
* **Until** : time at which notifications stop (e.g., `18:00`)

Times are to the **minute** : `09:00` or `09:00:00`, never `09:00:30`. A time with non-zero seconds is rejected on save.

**Add a slot** allows you to define as many as needed, with no limit on the number. A slot must end after it begins: a break in the middle of the day is therefore expressed as two slots (for example `09:00–12:00` and `14:00–18:00`), not by an inverted slot.

There is always at least one slot left: to stop filtering anything, turn off the toggle rather than deleting the slots.

### Time zone

The time zone is detected automatically from the user's browser (e.g., `Europe/Paris`). Configured times are interpreted in this time zone, for all slots.

## Behavior

* When the window is **active**, the slots are cumulative: notifications are sent as soon as**at least one** slot covers the current day and time
* When the window is **active** and no slot covers the present moment → notifications are not sent on the push and email channels
* When the window is **disabled** → notifications are sent at any time
* Overlapping slots are accepted and do not cause duplicates

## Examples

`active` and `timezone` describe the entire schedule; each slot carries only `startTime`, `endTime` and `daysOfWeek`.

* "Receive notifications only on weekdays from 9 a.m. to 6 p.m." → schedule `active: true`, one slot: startTime `09:00`, endTime `18:00`, daysOfWeek `[1, 2, 3, 4, 5]`
* "No notifications during my lunch break" → two slots: `09:00–12:00` and `14:00–18:00`, daysOfWeek `[1, 2, 3, 4, 5]` on each
* "On weekdays from 9 a.m. to 6 p.m., and Saturday morning" → two slots: `09:00–18:00` on `[1, 2, 3, 4, 5]` and `10:00–12:00` on `[6]`
* "Disable notifications on weekends" → schedule `active: true`, one slot `00:00–23:59` on daysOfWeek `[1, 2, 3, 4, 5]` : the window is always described positively; we cover weekdays instead of describing the weekend. The interface does not go below the minute, so `23:59` is the latest possible end. The end bound is compared to the second `00` of that minute: `23:59:00` is covered, but `23:59:01` at `23:59:59` are not — in practice the last minute of the day is silent down to the second.
* To stop filtering altogether, set the schedule to `active: false` — the slots are not deleted; there is always at least one left

## What the assistant can do

With the scope **Notifications** enabled, the assistant can:

* View the current schedule (slots, times, days, time zone, activation), provided it is enabled: once the toggle is turned off, the assistant can no longer see the saved slots
* Set up or modify the slots (the call replaces the entire schedule)
* Enable or disable the time window — to re-enable it, the assistant asks for the full schedule again, since it can no longer read it