Briana Perez

I agree. It would save our team so much time to allow those that review the resources this ability. We are a team of 2 and I review most of our knowledge base so it would be beneficial for us. 

I found out this week that there is not a way to allow users in our Knowledge Base to either see the article settings of an article (after it is published) or revisions without either granting them publishing permissions or updating their role. In our use case, it would be great for us to be able to use a user segment to grant access to both revisions and article settings. We have content owners from each of our departments and locations and as admins we have to refer to them to review the information in their articles, but overall our department will publish all changes. I was told we can allow article settings only on a role basis, but due to our various departments, we wouldn't want to grant all members of those teams in that role. And for revisions, we would love that we can give access to revisions without the ability to publish. That takes more work from our team in auditing to ensure nothing was published accidentally without us being aware. 

We would also love the ability to enlarge photos in Guide. Some screenshots just do not look good and attaching them makes updates more tedious. 

It would also be great if the a history of assignment notes were tracked somewhere.