https://community.fabric.microsoft.com/t5/Report-Server/Issues-with-Security-Roles/m-p/646370#M9825 <P>We've just upgraded from August 2018 to January 2019 Report Server.</P><P>&nbsp;</P><P>In the older version anyone with a "Publisher" role was able to publish a PBIX and create Folders and these new objects inherited security. A "Publisher" could not assign Security Roles.</P><P>&nbsp;</P><P>It appears that the Jan 2019 version has broken this logic and now someone with either "Publisher" or "Content Manager" role can assign security.</P><P>&nbsp;</P><P>This is a serious issue.</P><P>&nbsp;</P><P>It is also possible for a "Content Manager" to assign "Content Manager" permissions so security could quickly become an issue.</P><P>&nbsp;</P><P>Thanks</P> Fri, 15 Mar 2019 14:33:39 GMT saj 2019-03-15T14:33:39Z https://community.fabric.microsoft.com/t5/Report-Server/Issues-with-Security-Roles/m-p/646370#M9825 <P>We've just upgraded from August 2018 to January 2019 Report Server.</P><P>&nbsp;</P><P>In the older version anyone with a "Publisher" role was able to publish a PBIX and create Folders and these new objects inherited security. A "Publisher" could not assign Security Roles.</P><P>&nbsp;</P><P>It appears that the Jan 2019 version has broken this logic and now someone with either "Publisher" or "Content Manager" role can assign security.</P><P>&nbsp;</P><P>This is a serious issue.</P><P>&nbsp;</P><P>It is also possible for a "Content Manager" to assign "Content Manager" permissions so security could quickly become an issue.</P><P>&nbsp;</P><P>Thanks</P> Fri, 15 Mar 2019 14:33:39 GMT https://community.fabric.microsoft.com/t5/Report-Server/Issues-with-Security-Roles/m-p/646370#M9825 saj 2019-03-15T14:33:39Z