Skip to main content
LLMs.md

Shift defaults on the property

Instead of configuring check-in windows, minimum duration and similar settings on every single shift, you define the values centrally. Every shift inherits these defaults automatically — and only where a shift really needs to differ do you enter its own values.

Shift defaults on the property

:::info The principle: inherit instead of copy For each setting, a shift knows three states:

  • Default (inherit) — the shift takes the property's value; if the property maintains no own value, the default from the main settings applies. If you change the default later, all inheriting shifts follow automatically.
  • Own values — the shift has its own value that beats the default.
  • Off — the feature is deliberately disabled for this shift, even if the property or the main settings have a default. :::

The inheritance chain​

A setting is always resolved in the same order:

Shift → property → main settings → no rule

The shift itself wins (own values or "Off"), then the property's default counts, then the tenant-wide default from Settings → Shift defaults. If none of the three levels applies, the shift simply has no rule for this setting — and no violation check takes place.

Which settings are inherited​

SectionContains
Check-in windowTime window before/after shift start, requirement mode, number of required check-ins
Check-out windowTime window before/after shift end, requirement mode, "copy from check-in"
Auto check-outAutomatic check-out on/off and offset after shift end
Minimum durationMinimum duration per visit, minimum total attendance, grace period
InstructionsText shown to workers in the app

Times, recurrence, staffing and the customer order are not inherited — those stay with the individual shift. The reaction to violations (who gets alerted and how) is configured separately via the reaction defaults.

Setting a default on the property​

  1. Open the property and switch to the "Shift defaults" tab.
  2. Each section carries a select: "Default from main settings" (preselected), "Own values" and — where the feature can be disabled — "Off".
  3. Choose "Own values" — the input fields expand and must be filled in. The fields are the same as in the shift dialog.
  4. Save. A notice shows how many existing series without own values will adopt the default.

As long as a section is set to "Default from main settings", the property simply passes the central value through — if the main settings maintain none, inheriting shifts end up with "no rule".

Editing the tab requires the Edit properties permission.

How the shift dialog behaves​

In "Create new shift" (and when editing), the four sections check-in window, check-out window, minimum duration and auto check-out are grouped under "Attendance control" — right next to "Reaction on violation". Each section is a select with these options:

  • "Default: <value>" (preselected) — shows the inherited value and its source, e.g. "Default: 10 min before start, required — from property 'Apartment 02'" or "— from main settings". If no level provides a default, this reads no rule — the shift is not checked for this setting.
  • "Own values" — the familiar input fields expand, prefilled with the default as a starting point; the values are then required.
  • "Off" (where available) — deliberately disables the feature for this shift, even if the property or the main settings have a default.

You can return to the default at any time by picking the default option in the select again — the own values are discarded and the shift inherits again.

Instructions, material and check-alive remain "+" chips under More options: clicking the chip opens the input fields as a deliberate entry for this shift; if it stays closed, the inherited default (or no rule) applies.

Effect on existing shifts​

  • Series with own values remain unchanged — a new default on the property or in the main settings never overrides a deliberate exception.
  • Series without own values adopt the default for all future occurrences. Occurrences already generated in the past are not re-planned retroactively.
  • The automatic checks (minimum-duration monitoring, auto check-out) also use the inherited values immediately.

:::tip Recommendation Define the shift defaults in the main settings first, add own values only on properties that really differ — and then deliberately create "lean" shifts: just customer order, name, times and staffing. Everything else inherits. Your shifts stay consistent, and changes to the rules happen in a single place. :::