---
title: "Opening Mode Exceptions"
description: "An opening mode exception temporarily changes the opening mode of selected readers—for example, on public holidays, during a company event, or on an open house day. For the exception, you set the daily schedule, time schedules (when the exception applies), and the readers it applies to."
url: https://navody.aktion.cz/en/articles/117-opening-mode-exceptions
updated: 2026-10-13
language: en
alternates: [cs]
---

# Opening Mode Exceptions

An opening mode exception temporarily changes the opening mode of selected readers—for example, on public holidays, during a company event, or on an open house day. For the exception, you set the daily schedule, time schedules (when the exception applies), and the readers it applies to.

An opening mode exception temporarily changes the opening mode of selected sensors – for example, on holidays, during a company event, or on an open house day. For an exception, you set the course of the day, schedules (when the exception applies), and the sensors it applies to.

## List of exceptions

In addition to the name and note, the list displays the columns **Used for sensors** and **Next application dates**. Click a row to open the exception details.

## Creating an exception

1.  Click **New**.
    
2.  Enter a **Name** and, in **Daily schedule**, set which mode should apply during each quarter-hour. The editor has a single row, **Day**, and works the same way as the mode editor (see Time modes – schedule editor).
    
3.  Quarter-hours set to **Mode-based** do not change the exception; the sensor’s regular opening mode applies. A new exception is entirely **Mode-based**.
    
4.  Click **Create**. The exception details will open.
    

![“New opening mode exception” dialog with settings for the name, daily schedule, time schedule, and note. Visible: New opening mode exception, Name \*, Open Day, Daily schedule, Closed, Prohibited.](https://staticfiles.gleap.io/ghelparticle/cU2ZQWZyHr3GbVAWXzMu2ePJwKqYah8XKaHavNoFllJcDyR9zeFL8fn3AgG2oIZgLWNWibYwY4w.png)

## Time schedules

A time schedule determines which days the exception applies to. An exception can have multiple schedules.

1.  In the exception details, on the **Record details** tab, click **Add** in the **Time schedules** card.
    
2.  In the **Add time schedule** window, fill in:
    

-   **Valid from** and **Valid until**,
    
-   **Priority** – 1 (highest) to 10 (lowest); if multiple exceptions overlap on the same day, the one with the higher priority (lower number) applies,
    
-   **Recurrence** – **Daily**, **Weekly**, **Monthly** or **Periodic**; for **Periodic**, enter the **Period in days** (1–999).
    

1.  Click **Add**.
    

![The “Add time plan” dialog shows validity dates, priority, and recurrence settings, with “Daily” selected in the focused Recurrence dropdown. Visible: Add time plan, Valid from, 14.11.2026, Valid until, Priority, 1 (highest).](https://staticfiles.gleap.io/ghelparticle/W3cHwg6CXPJyXmPPhMHHrLo0GHIAq1zAiQc2FqUl0mZF6GVH8CvNGiWdLEWfrQZBbwQ4AkpXM4g.png)

![AKTION administration screen shows the “Open House Day” opening mode exception, with its daily schedule and time-plan table. Visible: Record details, HW structure, Result, No sensor has been assigned to the exception yet – it will not apply to any devices., Basic information, Name.](https://staticfiles.gleap.io/ghelparticle/zJJjknAyVzVubgrRo0GOxPBRYG2SjPqB3erW9spaf6J5DaGYyyx5NUa19RDcMo6olUJWletcpEK.png)

You can change the exception details (name, daily schedule, note) using the **Edit details** button.

## Assigning sensors

1.  Open the **HW structure** tab and click **Edit HW structure**. The table switches to edit mode.
    
2.  In the **Exception applies** column, click to select branches or individual sensors. The value is inherited through the tree in the same way as access—the selected branch applies to all sensors beneath it.
    
3.  The **Structure node details** panel on the right shows the selected node’s settings and where they are inherited from.
    
4.  Click **Save**. Click **Discard changes** to discard your edits.
    

Above the table is a summary of **Applies to … sensors**. Use the filter and the **Search structure** field to narrow the view.

![The AKTION Den otevřených dveří HW struktura screen shows opening-mode exceptions in an editable sensor tree, with test22 selected and its access exception set to Povolit in the detail panel. Visible: Den otevřených dveří, Detail záznamu, HW struktura, Výsledek, Uložená výjimka se do zařízení dostan](https://staticfiles.gleap.io/ghelparticle/dtVQAwN8N7NQ9VTvnxLOrWNczBUxVRIm4mBvZZtBYPOfKiCVS6cVz54T1DmHXKAu6cUKxdBZXUl.png)

## Result

On the **Result** tab, select **Sensor** and **Date from**. The resulting sensor opening mode for that day and the next six days will be displayed, including any other exceptions that apply to the sensor. Each day shows which exception governs it, or **no exception**.

![The “Resulting opening mode” section shows the daily schedule for sensor 0080A3A47B80-S1 from 13.10.2026, with no exceptions and Card or biometrics mode all day. Visible: Resulting opening mode, Sensor, 0080A3A47B80-S1, Date from, 13.10.2026, The sensor has no opening mode configured; Card or biometrics mode is assumed](https://staticfiles.gleap.io/ghelparticle/N5qQUGX9CzguQ8s77I20K5ysGMgfj08q4hWCnZ5L4kDvztQ91MAliHKePWRFy3CUghKJGwbx4MW.png)

An exception without a time schedule or without an assigned sensor does not apply to devices—the details will indicate this. A saved exception is sent to the device during the next full update of access points.