- Visible to everyoneincludes anyone who visits your help center and does not require sign in.
- Signed-in usersincludes internal and external users who create an account and sign in to your help center.
- Agents and adminsincludes team members only, so that you can create content that is internal-only.Note:Light agents are included in this segment. For a list of light agent permissions, see理解光和设置代理权限.
- Custom user segmentenables you to restrict viewing access to specific users based on tags, organizations, or groups by applying custom user segments, seeCreating user segments to restrict access.
You set view permissions at the article level, not the section or category level. You must be a Guide admin or an agent with publishing permissions to set view permissions for articles.
If visibility for all the articles in a section is internal, then the section will not be visible to end-users, but if one article in an internal section is visible to any end-users, then the section will become visible as well.
View restrictions do not apply to Guide admins. Admins can access all knowledge base content, regardless of the view permissions.
To set view permissions for an existing knowledge base article
- In your help center, navigate to the article you want to edit, then clickEdit articlein the top menu bar.
Alternatively, in Guide, click theManage articles(
) icon in the sidebar, then select an article from an article list to open it in edit mode. - ClickArticle settingsat the bottom of the sidebar.
- UnderVisible to, click the drop-down menu, then select an option to determine which users can view this article.Guide admins and agents with publishing permissions can set view permissions. Agents who do not have publish permissions anywhere will not see this option, and view permissions will default to agents and admins. You can make the article visible to:
- Everyone
- Signed-in users
- 经纪人和经理
- A custom user segment, seeCreating user segments to restrict access. Only twenty user segments appear in the drop-down; use search if you have more user segments.
Any articles that require users to sign in are not indexed by Google.
- ClickSave.
To set access restrictions in the community, seeApplying user segments to restrict access to community content.
35 Comments
Also would like to bump the need to be able to assign articles to MULTIPLE user segments. It would make managing accessmuchsimpler than having to create a new "segment" for each filter.
Hello, our company would like to restrict access to our help center to signed in users. But, we do not want just anyone to be able to create an account. We want to control who has an account for Help Center access. However, we would like to allow anyone to be able submit a ticket via email. Can you please point me to where in the settings we would enable such a restriction, (to have only admins and agent be able to grant KB access to users, but allowing anyone to submit a ticket via email).
thank you,
Bill
在这里你可以看到,howRestricting help center access to signed-in end-usersis possible to set up.
Here you can also find more details on this topic:
How do I remove the ability for customers to sign up for our account?
I think this is the right thread to ask this. Trying to see if it's possible to restrict access on some product articles AND is it possible to restrict access to an end user's ability to submit a ticket? Use case, clients in implementation have typically never had access to ZD, they get it when they 'go live', but I would like to grant access to specific product documentation and no access to ticket submission. We do have a free Brand we could use, but I would prefer not to do that.
Is there a way to see a log of changes to visibility permissions for a given article -- when did a change happen, to what permission, and by whom it was made?
I don't see this in the article Revisions or History.
Pleasesign into leave a comment.