Publish, duplicate and cancel shifts

Publish draft shifts one by one or all at once, duplicate a shift, and cancel a shift that no longer takes place.

BV
Björn von Känel
Written By Björn von KänelLast updated 19 days ago

A shift only becomes visible for your team when it is Published. Published shifts appear under Open Shifts, where people can apply.

Who can do this: shift managers.

▶ Watch the video

▶ Watch the video

  1. In Events → Shifts → Planner, click … at the end of a draft row. The menu offers View shift details, Edit shift, Publish, Duplicate and Delete. Menu of a draft shift
  2. Click Publish to publish this one shift. For a published shift the same menu offers Unpublish and Cancel shift instead. Menu of a published shift
  3. To publish several drafts at once, use the buttons above the list: Select … draft ticks all drafts, Publish … draft in this filter publishes all drafts that match the current filter. Confirm with Publish. Publish several drafts
  4. Duplicate creates a copy named "… (Copy)" as a draft. This works for standalone shifts; for event shifts it is refused, because each team may have only one shift per event.
  5. To call off a published shift, choose Cancel shift. The dialog tells you how many people get a cancellation e-mail (booked, pending or waitlisted). Click Cancel shift to confirm or Keep shift to go back. Cancel a shift
  6. The calendar icon at the top right shows the shifts in Month, Week, Day or Agenda view. Agenda view

Good to know

  • When you publish several shifts, each person gets one summary e-mail with the shifts of their teams, and each connected Slack team channel gets one message.
  • A cancelled shift stays in the planner as cancelled. Applications are kept for the history and nobody can apply any more.
  • The publish dialog currently says "1 people" when one person is notified; this wording will be fixed.

Related articles: Create shifts in the shift planner, Apply for an open shift, Review shift applications

Was this helpful?

Your feedback shapes what we write next.