Working rules
Configure organization working rules
Set the organization scheduling timezone separately from personal display time and configure the working-rule profile used by scheduling.
1. Set the organization scheduling timezone
Open Settings → Workspace and choose the organization's actual business timezone from Organization timezone. ElShift stores a named IANA timezone such as Europe/Helsinki and does not guess it from a user's browser, device or country.
The organization timezone is authoritative scheduling context and is separate from each signed-in user's personal display timezone.
Auto-Assign and schedule publishing require this organization timezone. Existing organizations with no saved timezone must select one before those actions can continue.
2. Enable Advanced Working Rules only when you need them
Open Settings → Workspace. Advanced Working Rules are optional organization-level configuration behind a master toggle. When the toggle is off, the detailed advanced rule editor stays hidden.
Organization Admins can change the organization-level setting. Other roles may be able to inspect the current configuration without receiving a write path.
Turning Advanced Working Rules off does not remove the required Organization timezone, rewrite existing schedules or delete the stored advanced configuration.
3. What belongs to Advanced Working Rules
Organization timezone is configured separately in Workspace because it is foundational scheduling context, not an optional Advanced Working Rule.
Break defaults apply to newly created shift data; they do not reinterpret existing schedules retroactively.
- Default weekly hours and the stored weekly-hours enforcement level.
- Minimum uninterrupted rest between shifts.
- Minimum continuous weekly rest.
- Night-work tracking start and end times.
- Whether new shift breaks default to paid.
- Optional source label, URL and effective date for the rule profile.
4. Treat enforcement levels as configuration, not a blanket guarantee
Not every advanced working-time calculation is connected to Auto-Assign as an automatic blocker. Rely on the warnings and blocks ElShift actually surfaces for the rule you are reviewing rather than assuming every field marked Hard is enforced everywhere.
- Disabled: records that the rule should not be applied.
- Warning: records warning-oriented intent for the rule.
- Hard: records hard-rule intent where the corresponding scheduling behavior supports it.
Working-rule settings provide planning controls and context; they do not establish legal compliance.
5. Set the organization scheduling timezone explicitly
Open Settings → Workspace and choose the organization's real business timezone from the Organization timezone selector. ElShift stores a named IANA timezone such as Europe/Helsinki; it does not guess the value from country, browser or device settings.
The organization timezone is authoritative for scheduling and employee-facing workplace dates. It is separate from each signed-in manager's personal display timezone.
Auto-Assign and schedule publishing are blocked when the organization scheduling timezone is missing. Existing organizations with no timezone must select and save one before those actions can proceed.
6. Save weekly-hours changes deliberately
When editing weekly hours, type the replacement value and commit it with Enter or by leaving the field. ElShift saves one completed edit instead of writing every keystroke and prevents a second overlapping save while the first is in progress.