Knowledge Base scope

[William Jones2]

I am trying to troubleshoot a new knowledgebase not being visible from the SP, even as admin. I have looked into the existing KBs and realized that while my new ones are setup the same there is one glaring difference.

The application scope of KBs that do populate on my widget in SP are all set to null. This cannot be changed (easily) and my new ones exist in global ( which is fine for our use). 

My questions are:

1. Is it at all normal to have KBs without a scope? Im not even sure how this was accomplished other than somehow removing global from the table itself?

2. Could custom configuration of the widget on portal be the culprit that is preventing my new global KBs from being visible? (note that trying to navigate to a KBA in the URL yields an access error, which also shouldn't be an issue given being an admin and the access/read being the same as all old KBs. Also, they are available platform side it is only a portal issue.

edit:

Update: I spun up a PDI and found that the KB Knowledge  Bases widget in my instance is the same OOTB widget in my PDI. So that likely isn't my issue.

[Jason Nichols · Accepted solution]

Hi William,

Have you added the knowledge base to the Knowledge Bases related list in the respective portal?

Configure knowledge bases for a portal

And yes, it is a bit strange that there are OOTB KBs with no scope. That seems to be the case with the KBs provisioned by ServiceNow (e.g., IT, Customer Service, Field Service Knowledge,...) But this does not prevent them from being displayed in portals. The Application field is mandatory, however for any new KB.

[William Jones2]

Thanks Jason, I like to know im not crazy.

FYI the root cause of the issue was that some one created empty UC that made it look like an existing group. Once that was corrected it works.