Publish, restore and export schedules

1. Publish schedules deliberately

Publishing sends the selected exact workspace and date range to Employee Hub. Later manager-side schedule edits remain private until the affected dates are published again.

Publish only the period you are ready for employees to rely on. Republish after approved swaps or other schedule changes that should become visible to employees.

2. Restore a published schedule snapshot

When a published schedule version needs to become the manager schedule again, restore it from the publication history instead of rebuilding it manually.

The restore workflow asks whether to keep or replace current manual assignments, and the same choice is enforced server-side. Restoring brings the snapshot back into the admin schedule; it does not automatically publish another employee-facing version unless you publish afterward.

3. Export schedules

Use schedule export/download when managers need a static copy of the current schedule. Exported files are not a substitute for publishing to Employee Hub when employees need the updated live version.

4. Choose the publish period with the calendar date picker

Publish Schedule uses a calendar date-range picker. Confirm the exact organization or department and the exact dates before publishing to employees.

5. Publishing requires the organization timezone

ElShift checks the current scheduling context before publication. If the organization has no configured scheduling timezone, publishing stops and asks an administrator to set it in Settings → Workspace.

6. Republishing an unchanged period is safe

When a published period is unchanged, ElShift now avoids rewriting identical published shift snapshots. The employee-facing result stays the same while unnecessary history writes and lock contention are avoided.