Shared calendars, operating schedules, time-window permissions, recurrences, and contextual restrictions.
Functional purpose
Scheduling and Time Management defines how Horus incorporates temporal rules into permissions, automations, and daily operation. It allows accesses, actions, and scenarios to depend on schedules, calendars, recurrences, or contextual restrictions.
Operating value
Temporal rules make it possible to delegate access for specific periods, activate scenarios at defined times, and organize repetitive operating routines. This reduces errors, avoids unnecessary permanent permissions, and adapts the platform to the real rhythm of each operation.
Included capabilities
| Capability | Explanation |
|---|---|
| Shared calendars | Allow users or groups to work over common time references for access, routines, and scenarios. |
| Operational schedules | Define periods when a function, device, user, or process is considered active or available. |
| Time-window permissions | Enable temporary access with start and end date and time, avoiding unnecessary permanent authorization. |
| Calendar-based automation | Executes actions or scenarios according to events, dates, schedules, or rules defined in a calendar. |
| Recurring schedules | Repeat actions in daily, weekly, or other patterns defined by the operation. |
| Contextual time restrictions | Adjust permissions or actions according to time, calendar, type of day, or operating context. |
Relationship with the Horus ecosystem
Scheduling connects with users, groups, permissions, automations, and dashboards. A calendar can determine when someone views a camera, when a scenario runs, or when an alert should reach a specific group.