Skip to main content
LoreLedger
All Guides

Game Masters

Game Masters

This guide is for GMs — the people running game sessions at a table in LoreLedger.

Your role as GM

When you create a game table, you are automatically assigned as its GM. Organisation Owners and Admins also have implicit GM-level access to all tables.

As GM, you can:

  • Manage table members (add players, change roles, remove members)
  • Create and edit lore entries with any visibility level
  • Create, edit, and delete sessions
  • Write GM-only notes that players cannot see
  • Track attendance
  • Create and manage quests and clues
  • Manage inventory (including the shared stash)
  • Upload files (session handouts, attachments)
  • Link sessions to lore entries and quests

Managing your table

Table settings

  1. From the table detail page, click Settings.
  2. You can update the table name and game system.
  3. Click Save Changes.

Note: Only organisation Owners and Admins can delete a table — GMs cannot delete tables.

Table members

From the table detail page, you can:

  1. Add members — choose from existing organisation members and assign them as GM or Player.
  2. Change roles — promote a Player to GM or demote a GM to Player.
  3. Remove members — remove someone from the table.

The last GM on a table cannot be demoted or removed.

Lore entries

Lore entries are the building blocks of your world's knowledge. They belong to a World and are shared across all campaigns and tables within it.

Entry types

TypeUse for
CharacterNPCs, PCs, notable figures
LocationPlaces, regions, landmarks
FactionGuilds, nations, organisations within the fiction
ItemArtefacts, magical items, notable objects
EventHistorical events, battles, discoveries
NoteAnything else — rules notes, setting details, meta information

Creating an entry

  1. Navigate to a world and click Entries, then Create Entry.
  2. Choose a type, enter a title, and write the body using Markdown.
  3. Add optional tags to help with filtering (e.g. "npc", "capital-city", "quest-hook").
  4. Set the visibility level to control who can see this entry. See Visibility and Spoilers for details.
  5. Click Create.

Editing and deleting entries

  • Click Edit on an entry's detail page to update it. Every edit creates a revision in the entry's history.
  • Click Delete on an entry's detail page to permanently remove it (Owner or Admin only).

Revision history

Every time an entry is edited, a new revision is saved. You can view the full revision history from the entry's detail page by clicking History.

Relationships

You can create relationships between entries to show connections — for example, linking a character to a faction, or a location to an event.

  1. On an entry's detail page, scroll to the Relationships section.
  2. Choose a target entry and a relationship label (e.g. "Member of", "Located in").
  3. Click Add Relationship.

Relationships are directional. When you link Entry A to Entry B, the reverse link is also shown on Entry B's page.

Tags

Tags help you organise and filter entries. You can add any tags you like when creating or editing an entry. On the entry list page, you can filter by type and tag.

For a deeper look at lore entries, see Sessions and Lore.

Sessions

Sessions represent individual play sessions at your table. They capture what happened with separate areas for players and GMs.

Creating a session

  1. From your table page, click Sessions, then Create Session.
  2. Fill in:
    • Title (required)
    • Session number (auto-suggested, editable)
    • Status — Planned, Completed, or Cancelled
    • Scheduled date and session date (optional)
    • Player summary — a recap visible to all table members (supports Markdown)
    • GM notes — private notes visible only to GMs and organisation staff (supports Markdown)
  3. Set the visibility level.
  4. Click Create.

Player summary vs GM notes

This is a key distinction:

  • Player summary is visible to everyone at the table. Use it for recaps, highlights, and what the party experienced.
  • GM notes are only visible to GMs and organisation staff. Use them for behind-the-scenes notes, future plot hooks, and things players should not see.

GM notes are enforced server-side — they are never sent to players, not merely hidden in the interface.

Session statuses

StatusMeaning
PlannedScheduled but not yet played
CompletedSession has been played
CancelledSession was cancelled

Attendance

On a session's detail page, GMs can set attendance for each table member:

  • Present — the player attended
  • Absent — the player did not attend
  • Excused — the player was absent with notice

Linking entries to sessions

You can link lore entries to a session to record which characters, locations, or events were relevant:

  1. On the session detail page, scroll to Linked Entries.
  2. Choose an entry from the dropdown and optionally add a context note.
  3. Click Add Link.

Linked entries also appear on the entry's own detail page, showing which sessions reference it.

For a deeper look at sessions, see Sessions and Lore.

Quests

Quests help you track objectives, story threads, and the party's progress.

Creating a quest

  1. From your table page, click Quests, then Create Quest.
  2. Enter a title and description (Markdown supported).
  3. Set the quest status.
  4. Set the visibility level. Quests default to GM Only.
  5. Click Create.

Quest statuses

StatusMeaning
RumourThe party has heard about this but has not engaged
ActiveThe party is actively pursuing this quest
StalledProgress has paused
ResolvedThe quest is complete
FailedThe quest was not completed

Clues

Clues are pieces of information belonging to a quest. They can be revealed or unrevealed.

  1. On a quest's detail page, scroll to Clues.
  2. Add a clue with a title, optional description, and optionally link it to a lore entry.
  3. Toggle the revealed status to control whether players can see the clue.

Unrevealed clues are hidden from players. GMs can reveal clues as the party discovers them.

Linking quests to sessions and entries

You can link quests to related sessions and lore entries:

  • Session links record which sessions involved this quest.
  • Entry links connect the quest to relevant lore entries.

For more detail, see Quests, Clues, and Inventory.

Inventory

Inventory tracks items owned by players or the party at your table.

Key concepts

  • Shared stash — items with no owner, representing communal party loot.
  • Player-owned items — items assigned to a specific player.

Adding items

Any table member can add items. As a GM, you can:

  1. From your table page, click Inventory, then Add Item.
  2. Enter the item name, optional description, quantity, and category.
  3. Choose an owner (a specific player, or leave blank for the shared stash).
  4. Optionally link the item to a lore entry.
  5. Click Create.

Players who add items are automatically assigned as the owner.

Editing and deleting items

  • The item's owner or the GM can edit or delete items.
  • GMs can transfer items between owners by editing the item and changing the owner.

For more detail, see Quests, Clues, and Inventory.

Uploads

You can upload files to worlds, lore entries, sessions, and quests.

Supported file types

JPEG, PNG, GIF, WebP, and PDF files up to 10 MB each.

Upload categories

CategoryWhere it is used
MapWorlds — for world maps and setting imagery
PortraitLore entries — character portraits and entry images
HandoutSessions — handouts for players
AttachmentLore entries and quests — general file attachments

Upload and storage limits depend on your organisation owner's plan. See Uploads and Files for details.

Visibility tips for GMs

Visibility controls are one of the most powerful tools for managing what your players can see.

  • All Members — everyone in the organisation can see this content.
  • Table Members — only members of a specific table can see this (useful for table-specific lore or sessions).
  • Organisation Staff — only Owners and Admins can see this.
  • GM Only — only GMs and organisation staff can see this.

Practical suggestions:

  • Use GM Only for session prep, future plot hooks, and unrevealed quest details.
  • Use Table Members for table-specific content in shared-world settings where different tables should not see each other's sessions.
  • Use Organisation Staff for administrative or meta-game content.
  • Quests default to GM Only — change them to All Members or Table Members when you want players to see them.

For full details, see Visibility and Spoilers.

Related guides