Common Holiday Settings

Flowtly Editorial Team2 min

In Flowtly, as a manager, you can establish common holiday settings for your organization to align your holiday management process with company policies and operational needs. These settings allow you to customize approval processes and categorize different types of holidays. To update these settings, navigate to the Settings item from the main menu of your organization and select the Time off types tile.

Approval Count

Approval Count defines the number of approvals required for a holiday request to be finalized and accepted. This setting ensures that holiday requests are properly reviewed and authorized before confirmation.

To set up the Approval Count for your organization:

  1. Navigate to the Settings item from the main menu.
  2. Select the Time off types tile.
  3. In the Approval Count section, enter the desired number of approvals needed for a request to be validated.
  4. Select Save changes.

For example: If you set the Approval Count to 2, employees' holiday requests will remain pending until two individuals with the designated role approve them.

Holiday Types

All holiday types can be found and adjusted in the Holiday types section, located below the Approval Count settings within the Time off types tile. Each holiday type has a specific color and icon for easy identification.

Flowtly offers a predefined list of holiday types, including:

  • Army leave
  • Client office visit
  • Coaching
  • Disease
  • Family matters
  • Marriage leave
  • Not paid leave
  • On demand leave
  • Pick up day
  • Remote work
  • Vacations

You can edit this list based on your company's policy. To prevent employees from requesting a specific holiday type, you can deactivate its status.

To manage holiday types:

  1. Navigate to the Settings item from the main menu.
  2. Select the Time off types tile.
  3. Scroll to the Holiday types section.
  4. Select the Pencil icon (Edit mode) next to the holiday type you want to modify.
  5. To deactivate the holiday type, untoggle Active.
  6. To activate the holiday type, toggle Active.
  7. To make a description mandatory when requesting this holiday type, toggle Description required.
  8. Select Save changes.

If Description required is toggled off, the description field will remain optional for that holiday type.

Carry-over

Carry-over lets unused time off roll into the next period instead of being lost. When enabled, four options control how it behaves:

  • Enable carry-over — turns the carry-over policy on or off for the organization.
  • Expiry date — the month and day on which carried-over days expire.
  • Max carried days — the maximum number of unused days that can roll over.
  • Consume carried days first — when requesting time off, use carried-over days before the current period's allowance.

These options are configured on the Time off settings page, not here.

Example use cases

  • Centralized approval: A large organization configures the Approval Count to require two levels of approval (e.g., direct manager and department head) for all holiday requests to ensure proper staffing coverage.
  • Streamlined approval: A small team with a flat hierarchy sets the Approval Count to one, allowing a single designated approver to quickly process holiday requests.
  • Custom leave categories: A company customizes its Holiday Types to include specific categories such as "Volunteer Day" or "Study Leave" to reflect unique employee benefits or industry-specific needs.
  • Policy compliance: An organization deactivates holiday types like "Marriage leave" or "Army leave" if they are not applicable to their current workforce or internal policies, simplifying the available options for employees.

Connection map

Refers toUses upDerived from
Documented hereDocumented elsewhere
holiday-request made against holiday-type. holiday-request submitted by person. holiday-request draws down leave-entitlement. holiday-request becomes once approved absence. leave-entitlement held by person. bank-holiday applies as absence. absence reduces capacity.made againstsubmitted bydraws downbecomes once approvedheld byapplies asreducesHHoliday request — An employee's request for time off, submitted for approval. Approving it is what turns it into leave the rest of the system counts.Holiday requestHHoliday type — The kind of leave a request is made against, e.g. annual leave or unpaid.Holiday typePPerson — An employee. The central record the rest of the workforce data hangs off — profile, documents, leave, benefits, rates.PersonEEntitlement — How much leave a person has for the leave year. A request draws it down; the balance is what remains.EntitlementAAbsence — Approved time off. It removes hours from a person's week before any booking is counted against it.AbsenceBBank holiday — A public, company-wide non-working day. It applies to everyone rather than being requested by anyone.Bank holidayCCapacity — A person's contracted week, less absence. Bookings are measured against their own contracted week, so 20 hours fills 83% of a 0.6 FTE and not 50%.Capacity

Related terms