Learn Mokapen

Closing days

Closing days define when the organization is not operational: national holidays, collective vacations, bridge days, inventory closures. You configure them in Organization settings → General → Closing days tab. When active, Mokapen uses those dates in certain modules (primarily public bookings and HR); in others it only shows a warning.

This guide explains how to configure them and, most importantly, the cascade: what gets blocked, what is merely flagged, and what is not connected at all. For the company profile see the General guide; for shifts and presences see the Shifts and Presences guides.

Where to find it and who can edit

Menu Organization → General → Closing days tab.

• Member (and above) — can open the tab and save closings (enable, import holidays, add dates).
• Owner — same capabilities; changes also appear in the Activity log.

No dedicated Premium plan is required for this tab.

How to configure closing days

1. Turn on the Enable closing days toggle. When off, Mokapen does not apply the closings calendar (even if saved dates remain in storage).
2. Choose the reference Country for official holidays. When you save with closings enabled, Mokapen may also update the organization's country in Information.
3. Use the year tabs (current year plus the next two): each year has its own list.
4. Add dates manually (date + description, e.g. "Summer break") or press Load holidays [year] to import the country's public holidays (only dates not already present).
5. Edit labels or delete individual rows, then Save.

Delete settings (red button) removes the closings configuration entirely. Disabling the toggle without deleting keeps the dates in the database but does not apply them.

Cascade: what is applied (and what is not)

This is the key part. Closing days are not a global block across all of Mokapen. Here is what the system actually does today:

1. Public bookings (form / booking calendar) — hard block

In public forms that use the booking calendar, dates present in the active org_closings are marked as unselectable (disabled). The customer cannot choose that date for a slot. This is the only "hard" block that closing days produce.

If you use Bookings with public forms, always configure holidays and collective closures before publishing the link.

2. Shifts and Presences (HR) — warning only

In the create/edit modals for shifts and presences, if the date falls on a closing day Mokapen shows a warning (yellow alert): you can still save. There is no server-side block preventing the creation of shifts or logging of hours on closed days.

In practice: closings help the team avoid mistakes, but an HR editor can still plan or record on that day (e.g. on-call duty, extraordinary opening).

3. HR reports — classified as holidays

In Shifts and Presences reports, closing dates (typically together with Sundays) can be treated as holidays in hour analyses. They do not block anything at creation time: they serve the data-reading layer.

4. What is not connected

• Tasks / projects / activity deadlines — there is no automatic block on task due dates when the day is a closing day.
• CRM appointments (internal calendar) — closings do not replace appointment rules; the calendar block applies to the public booking flow, not necessarily every type of internal appointment.
• Existing tasks — they are neither cancelled nor automatically rescheduled.

If you previously read that closings "prevent creating other deadlines", interpret it as follows: the marketing text is broad; the verified behaviour is block on the public booking calendar + HR warning + classification in reports.

Recommended process

1. At the beginning of the year: enable closings, set the country, load holidays for the current and following year.
2. Add collective vacations and inventory closures manually.
3. If you use booking forms: verify that closed days appear as unselectable in the public preview.
4. Align the HR team: on those days they can still create shifts/presences (with a warning) — define an internal policy ("do not save" or "on-call only").
5. Before monthly reports, check that the year's closings are complete.

Use cases

• Practice / clinic with an online form — holidays + August break: patients cannot book on closed days.
• Multi-location retail — national closings are the same for all locations; locations are managed in the Locations guide (closings are at organization level, not per location).
• HR with on-call duty — warning on a shift on a closed day; the manager saves anyway with an "on-call" note.

Frequently asked questions

Q: Do closing days block tasks?

A: No. There is no automatic block on task due dates.

Q: Can I create a shift on a closed day?

A: Yes. A warning appears, but you can save.

Q: Why can't the customer book on December 25?

A: If closings are enabled and that date is in the list, the public form calendar disables it. Check the Closing days tab and make sure the toggle is on.

Q: What happens if I disable closings?

A: Mokapen stops applying them (bookings no longer block those days; HR no longer warns). The dates can remain saved until you delete the settings.

Q: Are closings per location?

A: No — they are at organization level. Locations are a separate list (for shifts/presences).