DOMAIN SEPARATION: Can a Knowledge Base (not KB articles) be restricted (not viewable on KB homepage) by OOB parameters? A: (Y&N)

[Bill_Collins]

...e.g., User Criteria?

Title Changed 5.23.2017

---

Here's The Answer (Bug, Poor Engineering, or Sloppy Engineering?) :

Within a domain separated instance, User Criteria are not respected if set within a domain.     They will only be respected if set while in the Global domain.   Hence, a user assigned a domain (all users in an appropriately administered domain instance) with the knowledge_manager role can create KBs and set user criteria.   However, the knowledge_manager's efforts will not restrict access.   They can configure User Criteria.   It will do nothing.

We operate a pure domain separated instance, i.e., we are not an MSP cascading everything from the top.   Our customers have customers.   Process is set in the domains where it should be.   This ServiceNow failure prevents us from executing our business plan as our customers must rely on the tool owner (us) to assist in managing their KBs.

Message was edited by: Bill Collins

[Bill_Collins]

After further testing on multiple instances it has been determined I AM NOT crazy.   It is failing in a Domain instance.

[Bill_Collins · Accepted solution]

User Criteria are not respected if set within a domain.

[attilawinter]

Did ServiceNow fix this? They list Knowledge as having L2 domain separation support, but it does not seem to be the case.