How to Run a D&D Campaign in Notion

Notion works best when your campaign is a set of linked pieces, not a pile of pages. When quests connect to NPCs, locations connect to factions, and sessions connect to outcomes, you stop searching and start running.

Main question this guide answers

Answer: build a small set of databases, link them from a single session page, and run play from that page. Your goal is not perfect documentation; it is fast reference.

The simplest Notion setup (that still feels pro)

You don’t need a complex workspace. You need a small set of databases and a clean “Campaign Hub” page that points to what you’ll use during play.

• •Campaign Hub: your home base with links to the views below.
• •Adventures / Quests: what the party can do next, with status and rewards.
• •Sessions: one page per session with agenda, recap, and links.
• •NPCs: who matters, what they want, and where they can be found.
• •Locations: where scenes happen, who runs them, and what secrets they hold.
• •Factions: competing forces, clocks, and relationship notes.
• •Treasure: items, gold, and rewards linked back to quests and sessions.

Create a session page template (copy this structure)

• •Header: date, attendees, and a one sentence goal.
• •Recap: 5 bullets plus 1 open question.
• •Today’s beats: three scenes you expect could happen.
• •Linked references: quests, NPCs, locations, and items for tonight.
• •Rulings and reminders: quick notes you want at hand.
• •After play: consequences, loot given, and the next hook.

A session workflow that keeps prep low

Here’s a simple rhythm you can repeat every week. It works whether you improvise or run prewritten material.

• •Before (10-20 minutes): pick 1-2 quests, pull linked NPCs and locations into your session page, and write 3 short beats.
• •During: keep your session page open and click into NPCs or locations only when needed.
• •After (10 minutes): write a short recap and update quest and NPC changes while it’s still fresh.

Make the important stuff one click away

The best D&D-in-Notion experience feels like quick reference, not homework. Use relations so every name in your session agenda is a link you can follow.

• •If a name appears in your session notes, make it a link (NPC, location, quest, or item).
• •If you keep retyping the same thing, make a property or template for it.
• •If you forget it between sessions, put it in the recap and link it to what it changed.

Player-friendly sharing

Give players a read-only view of what they should remember: accepted quests, known NPCs, and session recaps. This keeps everyone aligned between sessions without spoiling secrets.

• •Share a Players view that hides secrets but shows quests, recaps, and known NPCs.
• •Keep a DM-only field for secrets so you do not have to duplicate pages.
• •Use one shared session recap page so everyone remembers what happened last time.

Common problems (and fixes)

• •Too many databases: start with Quests, Sessions, NPCs, Locations, Treasure.
• •Mid-session searching: move your links into the session page so you stay in one place.
• •Prep takes too long: limit yourself to 1 hook, 3 beats, and 1 reward.
• •Players forget context: begin every session with a 2 minute recap and a clear goal.