How to Keep "Any User" user criteria from adding back to Can Read

[BrownBear]

Whenever I try to add a User Criteria to the "Can Read" related list in a Knowledge Base and remove the OOB "Any User," the "Any User" user criteria does not delete. Does anyone know if there is an OOB business rule, UI Policy, data policy, client script, or ACL that is causing this behavior?? 

[Dr Atul G- LNG]

Hi @BrownBear 

It is not like that, the issue is with scope as well, i created KB in HR scope and found this issue. So better log a case with Now Support tean.

[BrownBear]

I just created a new KB in my PDI (Xanadu), and it created with all empty related lists including "Can Read."  Clicking Edit, I added "Any User" then saved it. I clicked Edit again, removed "Any User," saved it, and Any User was gone.

The only thing I can see different than what I tried prior, is this new KB was created with the "Global" application scope defined. I don't think there is a way to create a new KB with a blank application scope, is there??

[Dr Atul G- LNG]

Hi @BrownBear 

 I don't think there is a way to create a new KB with a blank application scope, is there --> NO, Atlleast Global scope will be there.

[BrownBear]

Thanks to a work colleague, we brainstormed this and determined the blank app scope is irrelevant to this issue. The issue with the "Any User" user criteria is due to cross-scoping. Per ServiceNow Support KB article KB0823727, the related M2M record for "Any User" needs to be deleted. This worked for me.

To remove the Any User user criteria:

1) under the Can Read related list, hover the cursor over the "i" icon to the left of Any User then click to open it.

2) Click Open Record

3) Change to the appropriate Application Scope to edit the record

4) Delete this [m2m] record

5) Observe the Any User user criteria is no longer present

6) The Any User user criteria still exists. Only the m2m record was removed. 

[Mark Manders]

Why would you want a Knowledge base without a scope? Using an application scope will only add it to that particular scope, so if you don't need a specific scope, it should be global.

What is your use case for creating it without?