yup, easily handled by the device, are the access points able to read vlan tags or are they basic consumer models?
Suggest you read the section on vlans here in terms of understanding
-
viewtopic.php?t=143620
But apply that knowledge like so.....
Using winbox, work through the Configuration Steps logically.
FIRST though, take one etherport and configure it so that it is accessible off the bridge to avoid getting locked out!!.
(
viewtopic.php?t=181718 )
Add Bridge (or modify default Bridge as required)
Add VLANS with the parent interface being the Bridge
Create Subnet Structure for each VLAN (and likely modify the default subnet to be one of the VLANs)
Construct /interface bridge ports ( etherports and WLANs as applicable )
Construct /interface bridge vlans ( tagged and untagged **** Should match up with /interface bridge ports as a cross-check )
Make Changes to LAN Interface List ( remove bridge and add all vlans typically)
Add Management/Base Interface List & applicable members (Base Vlan and off bridge etherport for example)
Adjust Firewall Rules as necessary (Base List to Input Chain, LAN List to Input Chain for DNS, etc. ( required router services ))
Go to CLI and run export and see if any errors crop up.
Turn on bridge vlan filtering.
You have to do the work, if you are not willing as it seems to be the case, suggest
https://mikrotik.com/consultants