© 2026 The ChroniclerHelpFor AI assistantsPrivacyTermsImpressumWiderrufAGBVerträge hier kündigen / Cancel contracts hereSupport
The Chronicler
HelpOpen the app
Help centre / Sessions

Recap release — who sees a recap and when

Recaps are held from players until released. Choose automatic release the day before your next session, immediate release, or hold for review.

On this page

  1. The three modes (Settings → Players & Sharing → Recap release)
  2. Release or pull back by hand
  3. What "released" controls
  4. Notifications
  5. A player cannot see a recap

A recap exists as soon as processing writes it, but players only see it once it is released. That gate is per campaign, with a manual override per session.

The three modes (Settings → Players & Sharing → Recap release)

ModeBehaviour
Day before next session (default for new campaigns)The recap is held and released automatically the day before the campaign's Next session date. If that date is not set, or the day before has already passed, it releases as soon as it is generated — the goal is to land before the table sits down, never after.
ImmediatelyReleased the moment it is generated.
Hold for my reviewStays held until you release it from the session page.

Set the Next session date on the same tab. It drives the first mode and is the only date the scheduler reads.

Release or pull back by hand

On the session page the recap panel shows Released or Held. The button beside it releases the recap to players, or pulls it back. Pulling back hides it from the portal again; it does not delete anything.

What "released" controls

  • The player portal lists a session with its recap only when it is released; otherwise players see "Recap not available yet".
  • Per-character recaps in the portal follow the same gate.
  • Public share links are separate: they are created by you on purpose and show the recap regardless. See Public sharing.

Notifications

You always get an email as soon as the recap is ready. Notify players when a recap is ready (same settings tab, off by default) additionally posts to your Discord webhook at that moment — keep it off if you use the hold mode, or players will be told about a recap they cannot open yet.

A player cannot see a recap

Nine times out of ten the recap is still held. See A player cannot see a recap.

Still stuck?

Email support@thechronicler.app and tell us which campaign and session you were looking at.

More in Sessions 8

Record at the table

Record a session straight from the browser. Audio is saved in one-minute pieces as you go, so a dropped connection does not lose the night.

Upload a recording

Upload an audio file up to 500 MB, a transcript file, or a Craig recording link from Discord. Long sessions should be exported as MP3 or M4A first.

Import a transcript or notes

Paste a transcript from Foundry VTT, Roll20, Fantasy Grounds or plain text, import a Roll20 chat log or YouTube captions, or turn old session notes into a session.

What processing does

Upload or record a session and we take care of the rest — transcribing it, working out who's speaking, and writing your recap and an updated wiki, usually within minutes.

Name speakers and voices

Tell The Chronicler who each detected voice is once; confirmed speakers are reused in later sessions and never relabelled.

Recaps and the three summary forms

Each processed session gets a Review, a Bullets and a Story version of the recap, all written from the same understanding of what happened.

Wrap up a session and lock canon

A short per-session checklist — speakers, new entries, merges, spellings — ending in Lock canon, after which nothing regenerates.

Highlights, handouts and PDFs

Approve the moments worth remembering, generate a "Previously on…" handout for the next game, and download a session as PDF.

← Back to the help centre