Who Can Do What

Who can do what

	Player	Trusted Player	GM
See and draw on a map the GM has shown	Yes	Yes	Yes
Move people, draw lines and groups, undo their own changes	Yes	Yes	Yes
Add, rename, reorder and delete maps in a collection	Yes	Yes	Yes
Rename a collection	Yes	Yes	Yes
Make a new collection	No	Yes	Yes
Make a new actor with New person	If allowed	If allowed	Yes
Hide or show a map	No	No	Yes
Delete a whole collection	No	No	Yes

Why it works this way

Every player can draw. Collections are ordinary journal entries owned by everyone at the table. That's what lets every player edit the maps, and Foundry sends each change to every other player straight away.

Making a collection needs Trusted Player. Making a journal entry needs Foundry's Create Journal Entries permission, which only Trusted Players and above have by default. The module doesn't widen that permission behind the GM's back. Once a collection exists, any player can add maps to it.

New person follows Foundry's Create New Actors permission. Players see the button only where the GM has given their role that permission. An actor a player makes this way can be seen by everyone at the table. One the GM makes stays hidden, like any new actor.

Hiding maps and deleting collections are GM only. A collection is a board the whole table has been drawing on, so the module keeps these to the GM even though Foundry itself would let any owner delete it.

Hidden maps

A new map starts out hidden. Players don't see its tab until the GM shows it with the eye. See Collections and maps.

Hidden maps are hidden from view, not encrypted. Like anything hidden in Foundry, a determined player with the browser console can still read them.

Per-map permissions

A shown map takes its permissions from its collection. If a GM uses Foundry's own ownership window to change the permissions on a single map, the window respects that: a player who can't edit that map isn't offered the tools to.