HomeProduct wikiPermissions and safe sharing
Campaigns & people 2 min read

Permissions and safe sharing

Check exactly what a player can view, edit or control before sharing your preparation.

The scene directory groups the broadcast scene and private scenes in a folder. Gravewright 0.3.0, English interface.
The scene directory groups the broadcast scene and private scenes in a folder. Gravewright 0.3.0, English interface. · Open full screenshot ↗

Understand the boundaries

The installation owner administers the host. A campaign GM manages that campaign. Players receive access through campaign membership and resource permissions. A streamer remains read-only. Server checks apply to actions and protected files; a URL or a visible button is not an access grant.

Actor and journal access use levels such as None, Limited, Read and Owner. The exact limited preview depends on the resource. Read access does not grant editing or token control. Scene access, token ownership, journal page access and GM-only sections are separate decisions.

Rehearse sharing

  1. Keep your GM session open and sign in as a player in a separate browser profile.

  2. Give that player the intended actor permissions. Verify that its sheet opens and that unrelated actors remain protected.

  3. Place the actor's token in a visible scene and test movement with the player account.

  4. Share one journal and one page intentionally. Include a harmless sample GM secret and confirm it is absent from the player view.

  5. Activate the intended scene for players and verify the broadcast.

  6. If you use a streamer link, inspect it independently of the player session.

Avoid accidental disclosure

Editor layer visibility in Map Builder is an editing aid: preview and generation include all project layers. Use the tabletop's GM visibility controls for private scene images. A screenshot, download or export can have a different audience from the live table.

Universal VTT omits GM-only images, but secret-door geometry may still be present in its exported file. Review it before sending it to players. Never assume that a campaign export is a player-safe handout.

When access looks wrong

Check the account, campaign role and explicit permission on the particular resource or page. Confirm that the intended scene is public and broadcast. Reconnect after permissions or memberships change to verify fresh authorized state. Grant the smallest access needed instead of making all documents public to diagnose one missing resource.