Skip to main content
Ilan B
Ilan B
Contributor ⭐️⭐️⭐️⭐️
July 7, 2021

Hide specific content elements

  • July 7, 2021
  • 3 replies
  • 51 views

Hi,

Currently, we can hide/show entire sections of content, dependent on the user roles.

I’d love to be able to gate/hide individual pieces of content within an open category. 

Use Case (Because @daniel.boon will ask me otherwise :wink:)
Internal / early releases
We are releasing a feature slowly. Before it is rolled out to all customers we want only specific customers, or even just only employees to be able to see the content. Currently, we do share the preview link, but I don’t think that that is a good practice. We also don’t want to have to move it to a hidden category, because it makes most sense where it currently is.

Thanks in advance. 

    3 replies

    M
    Marion Frecaut
    Helper ⭐️⭐️⭐️
    July 14, 2021
    Updated idea status New → Open
    M
    Marion Frecaut
    Helper ⭐️⭐️⭐️
    July 14, 2021

    Hello @Ilan B, thanks a lot for your idea. If I understand correctly you are asking for permissions at the topic level. I have to say, I am a bit afraid this would make permissions way complex.

    Thanks for sharing your use case. I'm curious at the different stage of the release of a feature, do you have the exact same communication? 

    Ilan B
    Ilan BAuthor
    Contributor ⭐️⭐️⭐️⭐️
    July 15, 2021

    Thanks @Marion Frecaut.

    I get the hesitancy, but I think it should be fine. It obviously should be used with precaution etc, but I imagine users who would use a feature like this to be prepared for the complexities. 

    With communication, it’s case by case. However, we do want the documentation to be ready so that Beta users can have all the information in front of them and we can use the same links in our product. This way, when we roll it out, all we have to do is open the article, and from a KnowledgeBase/Community perspective we are ready to go. Otherwise, we would have to hide the article somewhere, and create new links when the feature goes live, and potentially confuse users and lose community value. Yes, I know we can do redirects, but I don’t think that it’s a good practice.

    Ilan 

     

    Terms & ConditionsAccessibility statement