How to Share a D&D Session Recap on Discord Safely

To share a D&D session recap on Discord, I first decide which facts the players can read. A session record may contain a clean recap, a missed clue, a private motive and a full transcript. Those details do not all belong in a campaign channel.

CharGen has a Discord workflow for finished sessions. Where enabled, a campaign owner can connect the campaign to a channel. They can post a finished recap by hand or enable automatic posting. A separate player view link gives the group a readable session page. It hides the DM's notes and transcript, but anyone with the link can read it.

This guide covers the sharing step. It does not explain how to record a session or write the recap. For session capture, read my D&D session notes guide. For recap structure, use the spoiler-safe template. My session summary tool guide compares the options.

Keep the recap separate from private notes

A Discord post is the last step in a record workflow. It is a poor place to decide what happened. Write or review the session record first. Then choose the parts players should see.

That distinction matters because a DM's notes answer different questions from a player's recap. The DM may need a villain's hidden goal, a clue the group missed, or the reason an ally lied. The players need the events their characters witnessed, the choices they made and the next open problem. Putting both audiences in one paragraph makes a spoiler easy to miss.

I use a simple check before sharing:

A generated recap can still get a name wrong or treat a guess as a fact. Read the full text before you post it. If the session contains a reveal, compare each sentence with what the characters know. A careful two-minute edit is cheaper than running a scene after the whole party has read its secret ending.

This is also why I do not post a raw transcript as the recap. A transcript is a source record. It can contain table chatter, player plans and details that do not belong in a public summary. Keep it in the session record, then share the shorter player view.

The wider market is moving towards shared campaign journals too. D&D Beyond introduced Journals in May 2026 and later added player editing to its Player Journal. That supports a clear need: groups want a place to keep events and decisions between sessions. A Discord post has a smaller job. It should bring the group back to the same page without asking every player to search a long archive. Read D&D Beyond's Journals announcement and its September update on player editing for more detail.

How to share a D&D session recap on Discord

Start in the campaign's Discord settings. The control is called Connect a channel. Discord then asks you to choose a server and a channel. Select the channel where your players already read campaign updates. Avoid a general chat if your group uses it for unrelated conversation.

After you return to CharGen, check the channel name and the Connected status. The campaign settings also show Send a test post. Use it before your first real recap. This checks that the selected destination can accept a post. It does not publish a finished session.

There is a second route if the CharGen bot is already in your server. In the channel you want to use, run /campaign link. This links the campaign to that channel. The web route uses Discord's channel picker. Pick whichever path matches your setup.

Before you connect the channel, ask whether every member who should read it can see it. Discord's channel permissions use separate controls for viewing a channel, sending messages and reading message history. A recap channel may need View Channel and Read Message History for players. Add Send Messages if you want them to reply there. Discord documents these settings in its channel permissions guide.

Keep the channel's access rules in mind when you choose the destination. A post in a private channel is only useful to members who can open that channel. If one player cannot see it, check their server role and the channel's permission overrides first. Do not move a recap into a public channel just to fix one person's access.

The Discord connection belongs to a campaign, not one session. Later session posts use the same channel. Check the campaign and channel names before you confirm the connection. Do this carefully if you run more than one group in the same server.

Choose automatic or manual posting

Campaign Discord settings include Post when a session finishes. Turn this on if you want CharGen to post each finished session to the connected channel. The setting saves on its own. You can turn it off again if your group wants to review each session before it goes out.

I prefer manual posting when the table uses secrets, unreliable narrators or a long gap between sessions. That gives me time to correct spellings, remove guesses and cut details the players have not learned. Automatic posting can suit a group that has an established recap format and reviews its output in the session workflow.

For a manual post, open the finished session. In the session header, use the Post to Discord control. Once a post exists, the menu can show Posted to Discord, Open the post and Update the post. If a post fails, it can offer Try posting again. The session must finish processing before it is ready to share.

The campaign settings describe the Discord post as a headline with the session cover. A thread can hold the recap, spotlights and quotes. Without the CharGen bot, the post can go out as one message. Add the bot to get a thread with one message per section. Check the on-screen prompt because thread support depends on the channel connection.

I would start with manual posts for the first two sessions. Check that the message lands in the right channel and that the recap reads well on a phone. Then decide whether automatic posting will save useful time. A setting is not a substitute for an editorial check if the campaign includes sensitive scenes.

Share the separate player view when it helps

The session menu has a Player view section with Copy player link. This creates an unlisted link to a player-facing session page. The view can include the recap, story panels, character spotlights, quotes, people the group has met and the next hook. The DM's notes and transcript stay hidden.

Treat the link as a bearer link. Anyone who has it can read the player view. It is not an invitation to join the campaign. The reader does not need to find the session in a public listing. That makes it useful for a player who missed the game or needs a quick refresher. Share it only in a place the intended readers can access.

The player view and the Discord post are separate actions. You can post a recap to the connected channel without creating a player link. You can also copy a player link without posting to Discord. If you include the link in a message, tell players what it contains and whether it is safe to forward.

Use Make a new link when you want to replace an old link. The old one stops working when the new one is made. Use Turn off the link to revoke it without creating another. After you turn off the link, its shared URL stops opening. Any Discord message that contains it remains in Discord.

Revoking the player link does not delete the Discord message that contains it. If you posted the link by mistake, turn it off first. Then remove or edit the Discord message in Discord. Make a new link only after you have checked the right audience and the recap content.

I test player links in a private browser window before sharing them. This catches a cut-off URL or an old link that was replaced. It also shows if the page still needs the owner's account. Ask another player to open it too. A DM's logged-in view can hide access problems that players will see.

Use a short recap that works in a channel

Discord is easy to scan when the post leads with the event, not the backstory. I aim for a short opening, a few clear facts and one forward point. If a player needs the full chronology, link the player view. Do not make the channel message a second transcript.

Here is a sample for a campaign with a stolen harbour ledger:

The group left the salt market with the customs tag and a promise to protect Pell. Three ships are missing from the harbour book. Sella believes the erased entries lead to the temple archive. Next session starts at the locked archive door, with footsteps on the stairs.

That sample gives players a place, a decision, a named ally and an immediate question. It does not reveal that Veyra is covering for her sister. The DM can keep that fact in private notes until the group finds evidence.

I also check the headline and cover image. A title such as Session 18: The Salt Market works better than Campaign update. The image should help players recognise the session, not hide the text below it. If the session cover contains a secret character or villain, choose another image before you share.

A message can be shorter than the full recap. If your group reads on mobile, one paragraph and a short list often works. If a section is empty, remove it. Empty headings make a post feel unfinished and make it harder to spot the facts that matter.

Fix the common sharing problems

The feature is available only where the account and backend settings allow it. If the controls are missing, do not assume the session is broken. Check that you are the campaign owner and ask CharGen support whether the feature is active for your account.

If a Discord connection stops working, reconnect it from campaign settings. If a session post has the wrong wording, edit the recap first. Then select Update the post. Revoke the player view link if it should no longer be shared.

A ten-minute routine after the game

I use the following order when I want a recap in Discord before the group forgets the small details:

1. Open the finished session and read the recap once for facts.
2. Fix names, places and decisions that are wrong or incomplete.
3. Remove DM-only information from anything players can see.
4. Check the cover image and session title.
5. Open the player view link in a private window if you plan to use one.
6. Post to Discord or confirm the automatic post went to the right channel.
7. Update the existing post if you make a correction later.

This routine keeps the session record as the source. Discord stays the delivery channel. The campaign retains the longer notes. The channel holds a short reminder for the next meeting.

For more detail on choosing a tool and reviewing a recap, read my guide to D&D session summary tools. If your next step is to make notes from a recording or transcript, start with RPG Session Notes. If your recap needs a safer shape, copy the spoiler-free recap template.

If Discord recap sharing is enabled for your account, try it with one finished session first. Connect one campaign, send a test post, then share a reviewed recap with the group. Keep the private notes in the session record and send only the view your players need.

Review a D&D session recap→