Core feature

Player-Safe Views

The reason most Game Masters keep two sets of notes is that one of them has the answers in it. Keep one world instead, and decide per entry what your table can see.

A relationship map in player preview, with hidden entities and relationships absent from the view. — The same map in player preview: what your table sees, with the secrets gone.

Hide Any Entry

Visibility is a property of the thing itself, so the traitor can sit on the map with the betrayal hidden.

Entities and relationships
Events and whole eras
Owner-only map annotations

Preview Their Seat

Answer "what does my table actually see?" by looking, instead of by remembering what you marked.

Flip the map into player preview
Check the timeline the same way
Flip back and keep working

Hand One Over

Pro

Export a player-safe document that leaves the hidden entries out of the file itself, not merely out of the view.

PDF or Word, formatted to read
Hidden entries never reach the file
Give it to players without a second copy

Where the real wall is

Player preview is a rehearsal, not access control: it renders your own screen the way a player would see it, so it tells you what you have marked, not what a determined person could dig out of a browser. The walls that hold are the ones between accounts. Someone you invited as a Viewer, or anyone reading a collection you published, is served only what they are allowed to see, and a player-safe export leaves your secrets out of the file entirely. Use preview to check your work; use roles and player-safe exports to share it.

Common workflows

A shared map the table can browse

Let players explore the world between sessions without handing them the plot.

Hide the entries that answer open questions
Check it in player preview
Share the map, then reveal as the story reaches them

A handout that survives contact

Print the gazetteer your players are allowed to have, from the same world you run from.

Export the collection player-safe
Leave your annotations owner-only
Re-export whenever the world moves on

Tips

Hide the relationship rather than the character. A player knowing two people have met is usually fine; how they met is the secret.
Hide an era to keep a whole age of history back until the campaign reaches it.
Check player preview before a session, not after. It takes a moment and it is the only way to catch the thing you forgot to mark.

Related examples

Collaborative Session

Running a game from a map everyone at the table can see.

See the Collaborative Session example

Great Houses

A political web where half the connections are things nobody admits to.

See the Great Houses example

Relationship Maps

Time & Events

Collections

More on this: all features · pricing · FAQ. Signed in? The help button in the corner of the app has step-by-step articles, a keyboard reference, and a guided tour for every page.

Your world is already a web

Every connection you are holding in your head is one you could be looking at. Build your first relationship map free, and see the shape of what you have made.

No credit card required • Create your first relationship map free • Export your data anytime