Organisation dates

This page is for org admins. Dates in the sidebar lists every date that affects the whole organisation. Select Add date (on a phone, + then Date), choose What kind of date?, and fill it in. The kind can’t be changed afterwards. Past dates fold away under Show past dates.

Closures are the simplest way to give everyone a break at the same time, so start there.

Closures

Days your organisation shuts, like the Christmas break, up to 31 days at a time.

Left as it is, a closure is on the house. The days are free for everyone, whatever your bank holiday setting. Upcoming leave over them is given back, and desks booked on them are removed. If you remove the closure later, the days become working days again, and leave booked over them costs again.

Comes off Annual Leave allowance: turn this on and Folke books the closure as approved Annual Leave for everyone, on the days each team member would work. It books around leave they already have, never before their start date, and for anyone who joins later too. It doesn’t check allowances, so it can take someone below zero.

Team members can’t cancel their own closure leave, though an org admin can cancel theirs. To excuse someone who’s working through it, cancel their closure leave: any manager over them can before it starts, and an org admin or team manager can once it has. Folke won’t book them into that closure again.

Telling your team

Everyone is emailed about a new or changed closure 15 minutes after you save, so there’s time to fix a mistake: a quick correction still sends one email, and deleting it in time sends none. You aren’t emailed about your own changes. Nobody gets a separate “leave approved” email for closure leave.

Removing a closure makes those days ordinary working days again. If it didn’t come off allowance, leave still to come that’s booked over those days counts against your team’s allowance again, and the confirmation says so.

Everyone is reminded 10 and 3 working days before a closure. They can turn off both the announcements and the reminders in Notifications.

No-leave dates

Times you’d rather nobody booked, like a launch week. Keep them short, since each one stands between someone and a break.

• Left as it is, team members can’t pick the days as the first or last day of a request. A request can run across them, and those days cost nothing, like a weekend. An org admin booking for someone sees them marked but can still choose them.
• Warn only, leave can still be booked: the days can be booked and cost a day as normal, and approvers see them flagged.

Under Applies to Leave Types, every type starts ticked. Untick any it shouldn’t cover, keeping at least one. With every type ticked, a leave type you turn on later is covered too.

No-leave dates show where your team books and approves leave, not on the team calendar, and nobody is emailed about them.

Events

One-off dates like a team day or the Christmas party, on every plan. They show on the calendar, on My Leave, on the dashboard and in calendar feeds. Everyone is emailed when one is added or changed, and reminded 3 working days before.

Moments Pro

Yearly milestones, like the day your organisation was founded. They come round every year on the Moments page, where everyone can react, and nowhere else.

On Basic, moments are hidden from this list, not deleted, and only events can be added.