Hi, I’ve encountered the same issue on version 4.16.2, also community edition. Did you ever find a fix for this? For my use case, it’s not a huge problem to have all the content managers as super admins, but this is hardly a fool proof solution.
Hi, I’ve encountered the same issue on version 4.16.2, also community edition. Did you ever find a fix for this? For my use case, it’s not a huge problem to have all the content managers as super admins, but this is hardly a fool proof solution.