I’m new to MikroTik and RouterOS, and recently started building my network using MikroTik devices. I’ve purchased a hEX E50UG router, running RouterOS 7.18.2, and I have two cAP ac access points (RBcAPGi-5acD2nD) that I want to centrally manage using CAPsMAN.

My plan was to set up CAPsMAN on the hEX router so it can manage the wireless configuration for the two access points. However, I noticed that:
• There is no CAPsMAN tab visible in Winbox/WebFig
• Trying to enter /caps-man from terminal gives an error:
bad command name caps-man
• I also initially had no “Master Configuration” options when setting up provisioning

This led me to wonder:
• Is it still possible to use CAPsMAN on a wired-only router like the hEX E50UG?
• Are my cAP ac devices compatible with CAPsMAN under RouterOS 7.x?
• Why is the CAPsMAN configuration interface missing or incomplete?

In order of asking:

1- Yes but see further down
2- Yes and also here with a twist
3- Because default it is not present on Hex Refresh

Now the long story
Somewhere early ROS7 Mikrotik made Wave2 drivers for their AX-line of devices. Those were to be loaded as a separate package since legacy wireless drivers were present as default.
As of 7.13 they reversed everything, wave2-basics are default present in ROS7 package (but you still need to load the wifi drivers themselves for devices requiring them). For device running legacy wireless, you need to use wireless package.
Hex Refresh is a wired-only device but since it runs ROS7, basic hooks for AX-line are there. Also capsman for AX-devices since that one is higly integraded with the wifi menu.

If you want to use it as capsman for legacy devices, you need to add wireless package (it's in the extra packages zip file), reboot your router and legacy capsman will be there under wireless.

Now the twist ... cap-ac devices are also capable of running wave2 drivers (uninstall wireless, reboot, install wifi-qcom-ac package, reboot).
So if you are only using those devices as access point and nothing else, you can benefit from using those drivers on those devices. It makes a noticeable difference in wifi behavior !
And then you do not need to install wireless on Hex since capsman for wave2 is present as default.

But ... it comes at a cost. Flash space on cap AC is really limited and using those drivers will consume close to all space on that device.
Also, wave2 drivers are quite a bit different as far as VLAN handling is concerned when using it in combination with capsman so it might not be the wisest decision to jump into the pool feet first if you're not comfortable with that part yet.

I use my capacs with my hex without capsman its quick and easy to config. Your hair will not turn gray or fall out!!

And this takes back to the question on where exactly to draw the line between unneeded and convenient:
viewtopic.php?t=204733#p1057410

anav is reknown for having this line drawn a little below infinite , but for most people it is above 2 access points, for newcomers I would even shift it above 3, particularly when mixing different generation devices.

Of course if it is for the sake of learning/experimenting it is different, but otherwise for two AP's it is not worth it (IMHO).

All in all it is an "addition", I would first have everything working as it should manually/independently and only later plan/study the migration under CAPSMAN, particularly for older devices with the 16 MB storage, the risk to need to netinstall to upgrade is real (and netinstall, while doable, is not exactly fun, particularly for newcomers).