What the DM Approves
Players propose, your device decides. That is the whole rule, and it holds for every table message a player can send. What changes is whether you are asked about it.
There are exactly two gates:
- Movement asks you. A player's token does not move an inch until you tap Accept.
- Everything else in a turn is checked silently. Targeting, End Turn, Dash, and switching to act as a familiar or spell effect are validated by your device in the background. Valid requests just happen. Invalid ones vanish.
Chapter 24, Playing Your Turn, is the same story from the player's chair.
The move request toast
When a player drags a movement string and confirms it, a dark toast slides down from the top of the map on your Play tab, outlined in that player's color. It carries:
- A dot in the player's color and the line "Alice requests to move".
- A sub-label with the numbers: "Move 20 ft of 30 ft". If the request is longer than the movement they have left this turn, the sub-label turns red and reads "Move 40 ft -- OVER BUDGET (speed 30 ft)".
- An Accept button and a Reject button.
- A small x in the top corner.
Accept moves the token on every device and subtracts the distance from that combatant's movement for the turn. Reject clears the request and nothing moves. Either way the player's own screen only changes when you answer; their token never moves on their say-so.
The small x is not a third answer. It hides the toast and leaves the request pending, and that toast will not come back on its own.
Over budget is a warning, not a wall. The app tells you the move is longer than the speed you set for that character and then gets out of the way. If the player has a reason, accept it.
When you are not looking at the map
If a request arrives while you are on the Session or Atlas tab, the Play tab icon in the bottom bar picks up a small badge. That is true on a phone, a tablet, a Mac, and a Windows machine. Tap Play and the toast is waiting.
Dash, familiars, and spell effects
Dash is not a separate approval. A player choosing Dash sends it as a turn action, your device doubles their movement for that turn, and the next toast simply shows the bigger number: "Move 45 ft of 60 ft". Turning Dash back off returns the budget to normal.
Familiars and movable spell-effect tokens send move requests exactly like a character does, and you answer them the same way. A spell-effect token carries its own movement separate from its caster's, so its toast counts down its own number. Chapter 26, Familiars, Spell Effects, and Auras, covers those pieces properly.
Free exploration works the same way
The approval flow is not a combat feature. Outside a fight, when the party is just walking around a revealed map, a player dragging their token still raises the same toast, and it still waits for you. There is no mode where player tokens move on their own.
Your own tokens never ask
Monsters and every other token you control are yours to drag or tap into place directly. There is no request, no toast, and no delay. Move is a player tool.
The silent gate
For the other turn actions there is no prompt, because there is nothing for you to judge. Your device checks the mechanical facts:
- The request came from the player who controls the combatant whose turn it is, or from the owner of a familiar on the familiar's own turn.
- The turn it was sent for is still the turn that is running.
- For targeting, the token being marked exists, is on the map, and is visible.
Pass all of that and the action is applied and broadcast to everyone. Fail any of it and the request is dropped without a sound, and only the sending device is re-synced so its screen stops disagreeing with yours. Nothing reaches the table and no error appears on your screen.
That is why a player occasionally says "I tapped it and nothing happened". It is almost always one of three things: it is not their turn, the turn moved on while they were tapping, or the creature they tried to mark is still hidden. Say so out loud and carry on. Chapter 23, Managing Combatants, is where you reveal the creature.