Find the answer without searching the whole atlas.

Lore Atlas supports Google, Apple, and Lore Atlas email and password accounts. Use the same method each time unless the identities have been linked to the same Supabase user.

Yes. Apple can provide a private relay address. It behaves like the account email as long as Apple email forwarding is configured correctly.

Choose Log in on the Lore Atlas account form before entering an existing email and password. Registration is only for creating a new account.

Yes. Campaign roles are independent. Use the campaign picker or Campaigns page to move between campaigns you own and campaigns you joined.

The DM copies the private invitation link from Campaign settings. The player opens it, signs in, enters their table name, and accepts. No invitation code entry is required.

Yes. Enable approval on the active invitation in Campaign settings. New players send a request, and the DM approves or declines it from the same access panel.

Yes. Invitations can have a lifetime and can be revoked immediately from Campaign settings. Previously joined players keep their membership.

Only the campaign owner can delete it. Lore Atlas requires typing DELETE and warns that the campaign cannot be recovered.

Use the campaign picker or return to Campaigns. Owned campaigns appear under My campaigns and joined campaigns appear under Campaigns I play in.

Account settings follow you across Lore Atlas. Campaign settings control one campaign, including rules editions, blind death saves, completion confirmation, and session defaults.

No. Lore Atlas updates the existing campaign in one transaction, preserving its ID, memberships, invitations, character claims, player notes, sessions, and display links. It saves a private recovery point first and offers an immediate undo while no newer Atlas work has been saved.

Open Export from an owned campaign to download a versioned JSON backup. To restore it, open Campaigns, choose Restore backup, validate the file, and create a separate restored campaign. Existing campaigns are never overwritten.

Backups exclude memberships, invitation credentials, account passwords, character claims, player-private character state, and player collaboration identity records. Full backups preserve player memories for reference but do not recreate another person’s authorship during restore.

A full backup is for recovery and includes campaign progress, sessions, table prep, and embedded handouts. A template is for rerunning or sharing structure. It resets thread and quest progress and omits the party, sessions, handouts, and journal memories.

Open Export, choose Share and print, then open Private Atlas overview or Printable campaign recap. Choose Save as PDF in the browser print dialog.

A thread is a playable card representing an Event, Location step, Quest, Encounter, Challenge, Clue, Loot, or Milestone. Connections show how those moments relate in the adventure; reusable NPC and Place records supply context.

A Location step is a visit in the story flow. Its reusable Place record holds the geography, nested places, current state, NPCs, and every scene that happens there. Create the step from Add thread; create or edit the Place by itself in the World Library.

A visit is one chronological stop in the story. Rooms inside the same place can remain in one visit, while a later return can start another visit that still points to the same canonical location. Edit the first thread of a later scene to start and label a new visit.

Pinch on a trackpad or touch screen, or use the zoom controls. Fit shows the whole atlas. The pointer position anchors trackpad zoom so the canvas should not jump away from what you are viewing.

The quest may require a particular outcome from its parent quest. It unlocks only after that quest is completed, failed, or abandoned with the configured result.

The thread's Gate rule decides. Require every is the AND rule, and Require any one is the OR rule. Associations add context but do not unlock the destination.

A connection describes campaign flow, such as required, optional, success, or failure. An association adds context, such as an NPC, place, quest, handout, creature, or item, without saying that one thread follows another.

No. Lore Atlas updates the active route while preserving the earlier selection and the later change in Decision history.

Edit the Quest thread and change Quest status to Available, Accepted, or Active. When it ends, use Resolve quest and choose Completed, Failed, or Abandoned.

Yes, after the thread is revealed. Player notes wait for DM approval before the party can read them. Character-specific notes remain limited to that character’s player and the DM.

Edit the thread and add At-the-table prompts. Use Start the scene for an opener, Ask the players for a decision prompt, Respond when for a likely approach and NPC answer, and DM consideration for checks, consequences, or pacing. These prompts appear in the Run inspector and never enter player-facing views or exports.

They show party interest and intent. They do not accept, complete, reveal, or otherwise edit a quest or thread.

The thread stays in the DM atlas but is excluded from player-facing views. New threads begin DM-only by default.

Use the eye action on its atlas card. The revealed thread then appears in player-safe campaign views and refreshes Player Display.

Yes. Open Player preview from Campaign settings. It uses sanitized campaign data and does not save preview interactions.

No. Player views should receive only revealed, player-safe data. DM notes and private memories are not included.

Tonight’s Table is private preparation. Sessions schedules and records live play. Campaign Journal is the lasting player-safe history created after a session ends.

Meet now creates and starts a one-off session immediately, without requiring a scheduled date first.

Confirm the session was live when the activity occurred and that the session was ended. The journal is built from completed session records.

Yes. Players can add memories to completed sessions. Visibility controls keep private DM memories separate from party-visible memories.

Lore Atlas creates an in-app reminder when you open the app within your chosen reminder window. Set the window from the notification bell in the global header.

No. Clocks are a common tabletop planning technique and a Lore Atlas campaign tool. They track pressure or progress but do not replace checks, saving throws, or DM adjudication.

Yes, when the DM has authored the consequence. A failure can adjust a clock, change a location or passage, select a route, or create a belief. The resulting event is preserved and can be reversed from Decision history.

Open the bell in any signed-in header, then choose the settings icon. You can control session, invitation, character, loot, quest, recap, and reminder notifications.

An Encounter needs at least one monster. Add an SRD or Homebrew monster, then return to Run encounter.

It gives a battlefield effect its own initiative count. Use it for lair actions, hazards, reinforcements, or any effect that acts during rounds.

Choose Wrap up combat, record whether each enemy was defeated, escaped, or survived, then finish the encounter. This writes the outcome into the session record.

Enable them in Campaign settings. The DM rolls privately in the encounter runner. Three successes automatically stabilize the character and three failures mark the character dead.

Every prerequisite must be complete and any access challenge must be opened. Claiming during a live session opens assignment controls.

Yes. The Loot assignment flow can divide copper, silver, electrum, gold, and platinum across the party, with deliberate adjustments when needed.

It appears in the session history, Campaign Journal, and the recipient’s player dashboard.

Lore Atlas supports open SRD sources, including the configured 2014 and 2024 editions. Campaign filters let the DM choose which editions appear.

Lore Atlas can only redistribute material available through licensed or open sources. Product-identity and non-SRD content may require a separate official reference and cannot be copied into the public catalog.

Internal reference sheets keep your campaign context in place while showing a readable stat block or item page. Directly exposing raw API JSON is avoided.

No. Homebrew belongs to its owner and can exist privately or in the community catalog. Compatible entries can then be added to multiple owned campaigns.

Published content stays permanent because campaigns may reference that version. Create a new version to evolve it, or archive it when appropriate.

Original AI items are stored as system-owned Homebrew with a full Lore Atlas reference page. The Loot thread uses that same catalog entry.

Comments are plain text, profanity is blocked, and users can privately report content or comments for copyright, safety, spam, or accuracy concerns.

It uses the encounter and relevant campaign context needed to suggest a reward. The DM reviews the draft before any Loot thread or Homebrew entry is created.

The service may be temporarily unavailable or at capacity. Retry once, then use manual Loot creation so preparation can continue.

No. It uses a temporary, player-safe link. Scan the QR code on the second screen, then navigate it from the DM controls.

The Player Display dialog includes a live preview and remote viewport state. Use fit, pan, zoom, reveal, handout presentation, and blackout controls from the DM view.

Reveal makes a handout available for players to revisit. Queue prepares it for the current table presentation. Show now temporarily replaces the shared Atlas with that image until the DM dismisses it.

No. Only the Lore Atlas site owner should run a migration explicitly named by release instructions. Retry once and report what you were doing when the error appeared.

That is a product defect. Capture what you were doing and the friendly error text, then retry once. Do not attempt infrastructure changes.

Confirm the correct campaign, refresh once, and sign out and back in if authentication looks stale. Clearing site data removes local preferences and should not be the first step.