Closed rachel3834 closed 4 months ago
In mop-dev this issue was partly caused by the User's Group having a different name from the one used by MOP to automatically configure the permissions. I've amended the code to cope with this and reset the permissions for all current events.
For future events, I've verified that MOP's cronjobs should correctly set permissions as new targets come in.
I believe that this should resolve the issue but this is hard for me to test because I have a su account. So if anyone else sees this issue happening again, please feel free to reopen this issue.
Various non-superusers of MOP report having access to only some targets and not all, both in MOP prod and MOP dev.