How to Let Players Move Their Own Tokens While You Manage the Map
Give each player control of their character token, then limit player permissions on the map, terrain, and other scene objects. Set those permissions before play and test with a player account: token ownership and map editing are usually separate controls, but their names and scope vary by virtual tabletop. This setup keeps routine character movement in players’ hands while leaving the GM responsible for preparing and changing the scene.
Decide what “manage the map” means
Separate the scene into things players should move and things they should only see. Usually, players need to reposition their own character tokens. They may also need to move shared objects such as a party marker or a dropped item, depending on the game. The GM typically retains control over the background map, hidden creatures, walls, and scene changes.
Write down the intended permissions before opening settings. A useful baseline is: each player can move their own character; players cannot edit or delete the map; and the GM can move every token and change any scene element. If players should move allied companions or shared props, decide who controls each one instead of granting broad access to all objects.
Give each player ownership of the correct token
In a platform with per-character ownership, assign each player control of their own character only. In Foundry VTT, for example, the Actor permission called Owner allows a user to control and see from the perspective of that Actor’s token; Observer allows viewing and perspective without movement control, while Limited does not allow token control. Foundry’s Actor permissions documentation
In Owlbear Rodeo, the GM can turn on the Character-layer “Owner Only” permission and assign an owner to a character. With that setting active, players can update characters they own, while the GM retains the ability to move all images. Owlbear Rodeo’s permissions guide
Avoid assigning every character to every player just to make movement convenient. Broad ownership can let players adjust one another’s tokens, and in systems where token vision follows ownership, it may also affect what each player can see. Foundry documents that a user controlling several tokens with vision may see the combined area when no single token is selected. Foundry’s token guide
Restrict map and scene editing separately
Token ownership does not necessarily stop a player from altering other map objects. Check scene permissions independently: look for controls covering map, terrain, drawing, props, tiles, or deletion. Owlbear Rodeo separates create, update, and delete permissions by layer, so a GM can restrict changes to maps while enabling character interaction. Owlbear Rodeo’s permissions guide
In Foundry VTT, ordinary Player and Trusted roles have different general capabilities, while the Game Master role has administrative control of the world. Use the least broad role that fits the group; do not promote a player to GM merely to solve a character-token ownership problem. Foundry’s user and permissions guide
The exact boundary depends on the tool. A setting that blocks map deletion may still allow drawing or moving a prop. Read the description for each permission and decide whether it affects one layer, one player, or the whole room. If the tabletop offers only broad permission switches, you may need to keep a prop GM-controlled and move it on behalf of the group.
Configure a reusable character token
Before the session, place each character token on the active scene and verify that it represents the correct character or actor. In Foundry, a prototype token is the preset for future placements; a token already placed on a scene becomes an independent copy. Editing the preset does not automatically mean an existing placed token has every updated setting. Foundry’s token guide
Give tokens clear names or recognizable art so players can distinguish their pieces. If the platform offers adjustable name visibility or resource bars, show only the information that helps the group use the map. Leave advanced configuration, such as vision settings, under GM control unless players need to change it. Foundry notes that editable vision settings can expose more of the canvas in a preview, so test that access deliberately. Foundry’s token guide
Test the setup from a player’s view
Use a player account or ask a player to join briefly before the session. Check each of these actions:
Can the player select and move their own character token?
Can they move another player’s character?
Can they move or delete the map, walls, drawings, or GM-controlled tokens?
Does the character token show the expected name, bars, and visibility?
Can the GM still move every token and make scene changes?
A player who can see but cannot move a character may have Observer-like access rather than ownership, or the token may represent a different character than the one assigned. A player who can edit the map may have a broad layer permission, a higher role, or access to a separate drawing or prop layer. Change one relevant setting at a time, then repeat the check so you know which permission fixed the problem.
Set expectations for movement during play
Tell players which pieces they may move and when movement should pause for a ruling. A simple procedure is: the player describes the intended move, moves their token, and stops at a clear boundary such as a doorway, hazard, or enemy. The GM can then confirm the result, reposition the token, or reveal the next part of the map.
This keeps the map useful without making every drag a negotiation. If the tool supports measurement, agree whether players should measure before moving or move first and resolve distance afterward. Treat that as a table procedure, not a permission setting: restricting map edits will not tell players how your group handles movement.
Recheck permissions after changing scenes
Permissions may be tied to a room, scene, character, or individual token. When you switch maps, confirm that the new scene has the intended player restrictions and that each character’s token is still controllable. In Foundry, placed tokens are specific to a scene, so a token on one scene is not the same placed object as the character’s token on another. Foundry’s token guide
If a player reports a problem mid-session, check ownership first, then the token’s represented character, then scene-level permissions. This order tends to isolate the issue without changing unrelated access. Once it works, record the working arrangement in your session notes so the next scene starts with the same clear division: players move their characters, and the GM manages the map.
Sources
Actors — Foundry Virtual Tabletop — actor ownership levels and token control.
Tokens — Foundry Virtual Tabletop — token presets, placed tokens, vision, and scene behavior.
Users and Permissions — Foundry Virtual Tabletop — user roles and document ownership.
Permissions — Owlbear Rodeo Documentation — layer permissions and character owner controls.
