Relationships

Relationships connect campaign records so the table can follow the story without remembering which note mentioned which person, place, object, or session.

What relationships connect

Use relationships to connect:

• NPCs to locations, items, notes, sessions, and questlines.
• Characters to NPCs, locations, items, and personal threads.
• Items to holders, containers, maps, sessions, or clues.
• Locations to child places, maps, notes, and events.
• Sessions to the people, places, items, and questlines that appeared.

Why they matter

Campaigns become hard to resume when information lives in isolated pages. Relationships turn the workspace into a campaign memory: open an NPC and see where they appeared; open a session and see the unresolved item; open a questline and see the characters involved.

Practical examples

• Link a stolen relic to the session where it vanished, the NPC suspected of taking it, and the questline about recovering it.
• Link a character to a faction contact, a hidden location, and the private note section that explains the secret.
• Link a map to the location it represents and the session where players first explored it.

Visibility still applies

A relationship does not publish hidden material by itself. Players only see records their visibility allows. Keep spoiler-heavy details inside GM-only note sections when the connection itself should not reveal the twist.