Skip to main content

Blocked Periods

Manage restricted dates where leave requests are limited or require special approval.

Overview

Blocked Periods allow organizations to designate specific dates as "restricted" for time-off requests. When an employee attempts to request leave during these times, the system will flag the conflict during the request validation step on the Review Request page.

Managing Blocked Periods

The Blocked Periods tab displays a table of all restricted date ranges. The page header includes two buttons:

  • Add Blocked Period — Opens a modal to create a new blocked period.
  • Export xlsx — Downloads the table as an Excel spreadsheet.

Table Columns

ColumnDescription
Created ByThe user who created the blocked period.
Start DateThe first restricted date.
End DateThe last restricted date.
DescriptionA text description of the restriction.
Disallowed UsersSpecific users who cannot request leave during this period.
Disallowed RolesSpecific roles that are restricted during this period.

Creating a New Blocked Period

  1. Navigate to Absence Management > Blocked Periods.
  2. Click Add Blocked Period.
  3. A modal dialog opens with the following fields:
FieldDescription
Start DateSelect the first date of the restriction.
End DateSelect the last date of the restriction.
DescriptionEnter a description of the blocked period.
Disallow Holidays forMulti-select: choose Users, Roles, or both to define who is restricted.
Disallowed Users(Visible when "Users" is selected) Choose specific users to restrict.
Disallowed Roles(Visible when "Roles" is selected) Choose specific roles to restrict.
  1. Click Add Blocked Period to save.

Impact on Requests

When a user submits a request that overlaps with a blocked period:

  • Validation Warning/Error: The system detects the conflict server-side during the validation step.
  • User Notification: The user is informed on the Review Request step that the selected dates fall within a restricted period.
  • Prevention: Depending on severity, the system may prevent the request entirely or display a warning that the user can acknowledge.

Related: