Setting view permissions on articles with user segments

Return to top

7 Comments

  • Kelsey Davis

    Hi

    Not sure if there is something somewhere else, but while we're on the topic of permissions. Is there anything on the roadmap to provide permission to access an article on a case by case basis with a shareable link? For example I don't want an article sitting there available for anyone to stumble upon, however once working through the query I want to then provide an article answer to my customer and that customer only. I don't want to do this with user segments because I don't want "everyone" or "everyone signed in" or every in a group to be able to see it. Like how Google Docs sharing works.

    Thanks

    0
  • Lauren Ward

    Hello! Very helpful article here. If we are using user segments to create internal content, what is the best way to flag an internal article within search results? I understand that the internal article will not appear to external users, but is there a way to automatically flag on the search results page that an article is internal? Thanks for any insight!

    0
  • Annamarie Jackson

    How can I check the Visible to for ALL of my articles. I am getting reports that a few of my articles are not Visible to as they should be, so I would like to check them all, but I don't see Visible to in the Filters available for Manage Articles. How can I view that for ALL Articles in bulk?

    0
  • Amy Gracer
    1. Under All Articles, select the check box at the top to select all. 
      This will enable the option buttons along the bottom
    2. Click Article Settings > Change permissions.
    3. And then from Permission Type, choose Visible to
    4. And from Visible To, choose the correct user segment
    0
  • Erik Lynch
    Zendesk Customer Care

    @... - The default Copenhagen theme in Zendesk Guide has a built-in feature for flagging internal articles when viewing them in the knowledge base. For example, in my test account if I open a section to see the article list in that section, I can see lock icons next to any articles that are internal-only:

    This same icon appears when viewing the article itself:

    Within the default Copenhagen theme, the code that adds this icon can be found in any template where an article title could be shown, such as section_page.hbs or article_page.hbs, and the relevant code snippet looks like this:

     {{#if internal}}
    <svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" focusable="false" viewBox="0 0 16 16" class="icon-lock" title="{{t 'internal'}}">
    <rect width="12" height="9" x="2" y="7" fill="currentColor" rx="1" ry="1"/>
    <path fill="none" stroke="currentColor" d="M4.5 7.5V4a3.5 3.5 0 017 0v3.5"/>
    </svg>
    {{/if}}

     

    @... - That's a great suggestion. There isn't any current estimate for when something like that might be released, but I can certainly see why that might be a useful feature to have. I'd recommend creating a Community post separately for that with your use case to help get more visibility and votes on the idea. Then, others can share their use cases to further drive demand for that feature. 

    I hope this information helps!

    0
  • Cindy Stoutenborough

    Are there other settings that need to be changed to allow "Visible to Everyone"? It appears that if I set that for an article, it still is only visible to signed-in users. 

    Under Security settings, I found this: 

    "Require Sign In (is checked)

    Only allow signed-in users to access Help Center. Anonymous users will be asked to sign in."

    Is this why Visible to Everyone, really isn't everyone? Most of our help articles are for customers, but some need to be available to prospective customers that do not yet have a sign-in. 

    0
  • Brett Bowser
    Zendesk Community Manager

    Hey Cindy,

    You are correct and if you have Require Sign in checked, then visible to everyone will only be visible to everyone that has signed in. I would recommend unchecking that box and restricting content at the article level instead.

    Hope this clears up any confusion!

    0

Please sign in to leave a comment.

Powered by Zendesk