Step 1 - Basic Information

Have more questions? Submit a request

Welcome to Time Off Policies!

If you're brand new to this process, we recommend checking out the introduction article in this series.

Learn more.


The first step in creating a Time Off Policy is choosing the policy name, the type of time off it’s nested under, and the desired approval flow. Let’s get started!

Policy Name

GIF Recording 2024-02-28 at 4.46.16 PM.gif

This is where you can add a descriptive name that shows what or who this policy is for. Remember, the policy will sit inside the selected Time Off Type.

For example, the following might be policies created for different Vacation allowances:

  • 2 Weeks
  • 3 Weeks
  • Executive Vacation

Only admins can see the policy name.

Employees will see the name of the type of time off (eg. Vacation), but not the policy name.


Time Off Type

GIF Recording 2024-02-28 at 4.46.45 PM.gif

This is where you select what type of time off this policy will be nested under. You can select an option that’s listed in the dropdown, or create a new one if needed.

Time Off Types are like baskets

You can think of the Types as the parent categories and the Policies as the sub-categories within them. Policies are variations that live nested within a specific Type of Time off in Humi. This allows you to assign unique policies to different employees within your company.

You can have multiple policies assigned to a single type of time off.

Choose the Time Off Type carefully

The selected Time Off Type can’t be changed once the policy has been assigned to an employee.


Approval Flow

GIF Recording 2024-02-28 at 4.49.38 PM (1).gif

Select the applicable approval flow for this policy. This setting dictates how each time off request is approved in Humi.

Still need to set up Approval Flows?

Approval Flows must be configured before creating your time off policy. Click here to learn how.

When you’re happy with your settings, click Next to move on to Step 2 - Accrual Settings.

Was this article helpful?
1 out of 1 found this helpful