If your group runs a training every Friday, you should not have to create it every Friday. A schedule creates the session for you.
Sessions → Recurring → Create Schedule.
What a schedule holds
- Name — becomes the session title.
- Type — one of your configured session types.
- Repeats — every week, every 2 weeks, or every month.
- Days of week or Day of month, depending on which you chose.
- Start and end time — wall-clock time in your workspace's timezone.
- Max participants.
- Roles — opened on every session this schedule creates, so an auto-created session is claimable the moment it appears.
How the timing works
Times are in your workspace's timezone, set in Settings → General. This matters: the job that creates sessions runs on a server that is not in your timezone. Without this, a group in Central time asking for an 18:00 training would have got one at noon.
Every 2 weeks counts from when you created the schedule, so editing a schedule later does not shift which week it lands on.
Monthly uses a day of the month. If you pick the 31st, months without one use their last day — so February gets the 28th (or 29th) rather than being skipped entirely.
What auto-created sessions get
Exactly what a hand-made one gets: role slots opened, an announcement posted, the ping sent, the board updated, and type subscribers notified. The recurring path is not the quiet one.
Turning one off
Deleting a schedule stops future sessions. Sessions it already created stay — they are real sessions with real sign-ups.