Don

This would be great to have! Especially since some companies block access to YouTube. Those clients see a blank box due to their companies' firewall policies.

Katarzyna Karpinska For content blocks, we still need the ability to add classes and other HTML attributes like classes and style, in order to add custom in-house classes.Right now it only allows plain

and tag. Can't do any in-house customization. This is severely limiting content block usage. We should have the same HTML capabilities as the HTML editor in an article. We have an upcoming project where a content block could have helped update many articles at once, but we just found out that we can't.

Before anyone mentions it, yes 'Display unsafe content' is setting is enabled for our knowledgebase.

We release new features at a scheduled period of time with updated UI. The team has to update content ahead of time but not publish it until the feature has been released/updated. 

Content Block is great to update many articles at the same time, however, one issue with using Content Block is that it can't be scheduled, making changes to the Content Block will update any published article that's currently using Content Block - whereas we have a specific date it needs to be updated. Here's a reminder notification that shows up when you update a Content Block. 

By the way, Content Block is great, especially since you can now update the images as well! Scheduling Content Block, just like how we schedule articles will be really helpful in planning and preparing.

We request clients to follow an article to get updates when it's updated. Adding a comment helps alert the client that the article has been updated by us.To prevent spam messages, we need the ability to disable public comments while retaining internal comments that are customer-facing.

Basically, we want to post a comment so all clients that are following an article will get an update from us only - blocking clients from posting a comment that would send a notification to everyone that opted to follow the article.

Tetiana Gron - I don't believe that helps. We need the ability to block articles from a section from being searched altogether. Example, a release note section can pan out to 4 years worth of historic release notes. Adding labels to 100+ articles isn't feasible. Would just prefer to exclude articles from a section or category from appearing in the search.

We don't need to hide the articles from our clients, just block them from appearing in search.

+1

We tried a few different solutions. Not that many options other than deleting the miscellaneous and release note articles. Zendesk search hasn't been that great. You get better article suggestions within your own help center if you search on google than you would from Zendesk's built-in search 🤨.

Having the ability to choose which sections/categories should be excluded from the search can help us dramatically reduce the number of irrelevant articles. Especially considering the search in itself isn't that smart (the word can literally be in the title of the article and still show up on page 2).

Ability to make some agents admins over only certain categories in the help center.

• Allow some Admin agents the ability to publish for Category A only
• Allow other Admin agents the ability to publish for Category B only
• Allow Top Admin the ability to edit and publish for any category.

This will ensure team members working on internal articles don't edit or publish external articles without limiting their admin permissions for the internal help center.

Having the ability to exclude articles or all articles in a section from appearing in a search will be really helpful.