Lindsey

Katarzyna Karpinska There is no commenting feature, and that is very needed. 

With our documentation in Guide, it is essential for us to have features common to writing software, like internal comments and collaboration within the editing view of an article. We often have just one or two questions about an article that we need someone to look at. It is inefficient to have to pull the article out of Zendesk to collaborate on it or to send a screenshot to someone. Many users in our organization are surprised that we can't collaborate within Zendesk. Ideally we should be able to highlight parts of the text and leave an internal comment on those and tag an internal user/agent in them to look at. 

Hi Jupete Manitas,
Thank you for your response. The problem we are facing is that there is no way to add suggestions, or comments, or have a discussion about small sections of the text. This is a very common feature in all other writing tools. Since Zendesk has no way to import those documents, it means we need to collaborate in a writing program and then copy and paste it to guide once it is finished. Even Freshdesk has this feature. Does Zendesk plan to add this feature anytime soon or are any add-ons that offer this feature? We need a way to collaborate on content and then seamlessly publish to guide and we also need to be able to comment and collaborate on existing articles. Assigning a developer a 600-word article for review when they only need to approve information in one sentence is not efficient, and that is the only collaboration Zendesk allows. 

Hello, 
So far I have found no way to collaborate on articles in Guide other than by submitting articles for review. Is there a way to collaborate with other authors by leaving comments and tagging agents?

Or, does anyone have an add-on that does this that they can recommend? 

We have one article we keep behind sign-in. We are worried users will not sign - in, go to this bookmarked article, or reach it from a link, and see "You're not authorized to access this page". Is there a way to redirect them to the sign-in page if they access this link and they are not logged in? 

Would a work around like this be possible for one article that is behind sign-in?