Expert
ExpertI still have not found a solution to my problem but I did want to offer a warning. Normally, any role that has "Threshold" and "Manage" on a Resource Group can set a custom threshold on an instance. But for that role, if you dare to attach an Access Group to it, LogicMonitor for some weird reason ADDS A NEW REQUIREMENT!
If you have any Access Group added to a role, for whatever reason, you all of a sudden have to have the checkbox set on the "Resources: Group Threshold" checkbox under the default Access Group. I'm not actually sure if this condition is added to the portal as a whole, or if it just messes up the role with an Access Role attached.
I found this out because my group I'm trying to give access to, for Access Groups, suddenly couldnt change any instance thresholds AT ALL. And I had to dig around and find out.
https://www.logicmonitor.com/support/threshold-management
So proceed with extreme caution!!
ExpertThankfully it looks like the reason that role lost access to edit thresholds is somewhat my fault, but the warning still stands. I added the Access Group to that Role specifically because I didnt want them to be able to edit Modules like they used to be able to, so I had unchecked the whole Default row except for view, not knowing that the "Resources: Group Threshold" was a new feature.
So it was somewhat my own fault, and the good news is that other groups should be fine as long as you dont uncheck that .... but again, the warning stands because obviously, when you want to use Access Groups for a role, the reason you want to do it, is because you dont want them messing with official modules.
But whatever you do, do NOT uncheck group threshold permissions from the default row. Because it OVERRIDES the manage and threshold settings on the Resource tab!!
