Token Action buttons not showing for players

I am running two DND5e games using the standard 5e character sheet and am having an issue with the NPC-init token action.  As a GM, everything is working correctly.  I see that button appear for any token on which I click.  I have also made a couple of rollable tables for magic items that I have flagged as token actions and they show up as well with no issue.  However, none of these show up for my players when they click on their tokens.  Even if I turn on the macro bar, they only get a blank bar.   I would have assumed this was a GM-only functionality but, when I use the "log in as player" function, the buttons show up and work correctly for me.  I can't figure out why it works for me as GM and when logged in as a player but not for my players.  My son is a player in my games and I've given myself access to his character/token and logged in as player and it works fine.  He then logs in on his PC and uses the same token and it doesn't show anything. I'm at a loss as I've validated the tokens are correctly linked to sheets, token action is checked, etc. and they still don't work in my games.  However, I am a player in another 5e game and it does show for me.  I have to be doing something wrong or have a setting incorrect but I can't find it. Hoping someone here can point out my error. FYI -- these are all marketplace content (Storm King's Thunder and Forge of Fury are the two games) with no customizations.

If these are collection/global macros; Check and see if you have enabled "Visible to Players".  Option is set per macro.  Also, each player will still need to enable the macro bar from their sidebar>collection>settings as well as check to show it on their screens.

Thank you!  Below is what my default view of the macro window looked like.  I didn't even notice the scroll bar on the right since the window looked complete.  I figured I had to be missing something simple and I was correct. :)

Its even worse than that though because the drop down also requires a scroll down after as well, its actually comical how they haven't caught this one yet and its just one of many things we all just learn to adapt to that they could easily fix with a simple change of 1 line in the code.  

It's probably not quite as simple as one line (since some of the pop-up box classes are shared, and changing one can result in undesirable changes on others), but it's not too much more complex. The interface has small issues like this all over the place.