"You do not have sufficient privileges to access this knowledge item" when trying to access publickb
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2023 11:45 AM
Hello,
I am trying to make a specific KB document public. I have went to the sys_public and listed kb_view as public. I have also made the kb homepage public. From the KB itself, I am getting a message saying "the kb_view UI page is public-users are not required to log in to view knowledge articles. Because of this, I have left 'roles' empty. I also have 'can read' empty. I still get a message saying that I do not have sufficient privileges when I try accessing this from a browser where I do not log in. Any suggestions on what I might have missed?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2023 11:56 AM
@Brent Cox Please go through this support article and check if addresses your question https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0787527.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2023 12:06 PM
Hello, this is what I tried first. I have kb_view set to public and then I kept can read and can contribute blank for the KB. I then tried leaving both blank for the document itself and I tried setting it to 'any user.' In either case, it still gives me the error that I don't have sufficient privileges.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2023 12:22 PM
@Brent Cox Could you try the solution suggested by Mark Stanger here https://servicenowguru.com/system-definition/controlling-public-availability-knowledge-base-content/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2023 12:51 PM
I did what the article said, everything except the ui macro. I will try that tomorrow. However, it looks like that is ONLY for making specific articles need a login. Everything should be open already as public based on the changes I have made. But unfortunately, I still cannot access the article. I took over the system a little over a year ago, but I worry there was some additional security that was added that I can't figure out.