timconner

Hey MichalJ, These are custom policies not predefined ones. I have indeed moved them to an Access Group where the users have a Permission Set granting them all the proper permissions. They wouldn't even be given the option to edit the policy if they didn't. However, I still receive this error.

I have a couple of ESMC users who have limited access to specific static groups. They specifically have Read, Use, and Write permissions to Policies on these static groups. However, they are unable to view or edit any policies that they have permissions to. Any attempt to simply view the policy in ESMC or edit are met with this error: ERROR WHILE INITIALIZING CONFIGURATION EDITOR. The only way to get this working is to seemingly give them Read permission on Policies for the All static group. This allows them to see some policies I'd prefer they didn't. Running the following version on Windows Server 2016: ESET Security Management Center (Server), Version 7.0 (7.0.577.0) ESET Security Management Center (Web Console), Version 7.0 (7.0.429.0) Is this a known issue?