It's under the client IP assignment section https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/SSID_Modes_for_Client_IP_Assignme...
L3 roaming is specifically for when you say for example have 3 floors with layer 3 subnets pushed to the access layer. So, clients get IPs in subnet 1, 2, 3 depending on which floor they're on. If devices are going to roam from one floor to another (meaning actively using device during the physical move) then layer 3 roaming is a good option.
If however a user will move and say carry a laptop, tablet, etc with them from their desk on 1st floor to a conf room on floor 3 that's not really a use case or need for L3 roaming. Standard mapping of the SSID/APs to their respective floor VLAN ID with bridged mode is fine.
Time and time again I see dashboards with L3 roaming enabled and mapped to a single VLAN. That does literally nothing different than standard bridged mode to a single VLAN 😉
Btw this is all explained in great detail here https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/...
Ryan If you found this post helpful, please give it
Kudos. If my answer solves your problem please click
Accept as Solution so others can benefit from it.