Tapestry Handbook

User Manual

Tapestry
Tapestry
›
Handbook
›
Permissions and Visibility

Players and sharing

Permissions and Visibility

Understand campaign roles, sharing audiences, content-level controls, and player-owned privacy.

GM + Player

About 9 minutes

Campaign roles

Owners control campaign-wide settings, integrations, data operations, and collaborators. GMs build and run campaign content. Viewers can inspect the GM workspace without changing it. Players use a separate workspace containing only shared and player-owned content.

Choose a sharing audience

  1. Share with All Players when the information is common campaign knowledge.
  2. Share with one or more player groups when parties should have different knowledge.
  3. Share with individual players for personal hooks or discoveries.
  4. Combine groups and individuals when an exception needs access without widening the whole audience.

Choose what the audience receives

Audience and content are separate decisions. A shared entity can expose its summary while withholding notes, portrait, type-specific metadata, and custom fields.

  1. Use the summary for the safe at-a-glance identity.
  2. Share all notes only when every passage is ready for players.
  3. Use partial note sharing for selected player-safe passages.
  4. Share portraits, metadata, and custom fields independently.

Important

Names and summaries can contain spoilers. A technically correct field configuration cannot make spoiler-heavy wording safe.

Visibility matrix

GM-authored entities begin private and require an audience plus at least one shared content area. Player-private entities belong to their author and may optionally be reviewed by the GM. Player-communal entities remain with the group in which they were created and are always visible to the GM.

Communal journals follow the same group boundary. Private journals remain author-only unless the player enables GM review. View as Player is read-only and does not bypass these rules.

Verify before a reveal

  1. Open Campaign Settings, then Players.
  2. Choose View as Player for the intended recipient.
  3. Check the entity list, detail page, search results, and calendar when applicable.
  4. Return to the GM workspace and adjust the audience or content controls if anything is missing or exposed too early.

Best practice

Test with the most restricted intended player. Broader access can hide mistakes that affect only an individual or small group.

The View as Player preview for Documentation Player Two, a read-only list of the content currently shared with that player.
Preview the exact read-only view a player sees before revealing anything.