Give your players the wiki without giving them your notes
Every DM with campaign notes eventually wants to hand players the parts that are not secret. The hard half is the second word in "read-only".
A link, not an invitation
Sharing produces a URL. Players open it and read the wiki; they do not create an account, they are not added to your campaign, and they cannot edit anything. For a table where two of five players will install nothing, that difference decides whether the wiki gets read at all.
The shared view stays current. As later sessions transcribe and new entries appear, the same link shows them — so it is one URL you paste in your Discord channel once, not an export you redo every week.
- No account, no install, no app — it opens in a browser
- Read-only: players cannot edit, add or delete entries
- Updates as new sessions process, from the same link
- Revoke it at any time and the link stops working
GM notes are not sent, not hidden
Every wiki entry can carry private GM notes, and those are excluded from the shared payload on the server, on every read path. They are not rendered white-on-white or toggled off in the interface — they never reach the browser, so there is nothing to find in the page source.
The shared payload is a whitelist rather than a filter, which is the safer direction: a new field has to be deliberately added to the public view rather than deliberately removed from it. A field nobody thought about defaults to private.
The link is a credential, and is treated as one
Anyone holding the URL can read the wiki, so the token in it is a bearer credential. Three things follow from that, and they are worth knowing before you paste it somewhere public.
Share links expire after at most 90 days, so an old link in a dead Discord server stops working on its own. Tokens are stored hashed, so a copy of the database does not hand anyone a working set of share URLs. And our robots.txt asks crawlers not to index /shared-wiki/ at all — a share token in a search result would be the link leaking, and refusing the crawl beats asking for deindexing afterwards.
What players actually see
The entries, their categories and the relationships between them, plus a session list — names, numbers, dates and durations — so a player can see the shape of the campaign as well as its cast. Cancelled sessions are omitted.
They do not see transcripts, recordings, or anything you marked as a GM note. The wiki your players read is a genuinely different document from the one you work in, assembled from the same entries.
What this does not do
It has no per-player permissions. There is one shared view, the same for everyone with the link. You cannot show the rogue one thing and the cleric another, and if you need that, this is not it.
It is not a login. Anyone with the URL can read it, including someone a player forwards it to. Treat it like an unlisted video link rather than a password-protected page.
Players cannot contribute. It is read-only in both directions — no player-authored entries, no comments, no corrections. A player who spots a mistake has to tell you.
And it shares a wiki, not a world you have not played. Everything in it came out of sessions you recorded.
Which plans include it
Sharing requires the Dungeon Master plan ($7.99/month) or Guild Master. It is the one thing on this list not included on the free Adventurer tier — the wiki itself is free, publishing it to players is not. See what each plan includes.
The rest of what it does
- Session transcription that already knows your characters’ names
Upload a session recording and get a timestamped transcript. Your wiki’s character and place names are fed to the model, so fantasy nouns survive.
- A campaign wiki that is written by the session, not after it
NPCs, locations, items and factions are extracted from your session transcript into a linked wiki you can edit, share with players, and search.
- Session recaps you can read at the table without editing them first
A "previously on" recap generated from your session transcript, with key events, decisions and cliffhangers. Regenerate, hand-edit, and keep old versions.
- Ask your campaign a question and get an answer with citations
Ask what the party promised the duke, or who gave them the sending stone. Answers come from your own sessions, with citations you can click and check.
- A relationship map of everyone your party has tangled with
See how NPCs, factions and locations connect — built from your session transcripts rather than drawn by hand, and editable where the AI got it wrong.
- Already have the transcript? Skip straight to the campaign wiki
Bring a transcript from Craig, Whisper or another tool. Get entities, a wiki, a relationship graph and a recap — on every plan, spending zero audio hours.