
- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 10-30-2019 01:16 PM
Knowledge OOTB - Documentation gap - Ownership groups and User criteria in knowledge articles.
Use case: Control access to knowledge articles using user criteria as per Servicenow documents/release notes.
https://docs.servicenow.com/bundle/geneva-servicenow-platform/page/product/knowledge_management/reference/r_MigratingKnowledgeAccess.html
Understanding user criteria and ACLs in knowledge v3
https://hi.service-now.com/kb_view.do?sysparm_article=KB0550924
Issue: ownership group overwrites the access controls set using user criteria on knowledge base/article.
No documentation on servicenow site describing this behaviour. Servicenow documentation mentions "Ownership group users who are either members or manager of groups assinged to an article will have access to contribute to articles even if they don't have contribute access to knowledge base."
https://docs.servicenow.com/bundle/newyork-servicenow-platform/page/product/knowledge-management/task/t_SelectUCArticle.html
Servicenow product team confirmed the functionality of ownership group being priortized than the user criteria is the expected behaviour. Ownership group feature created for managing the article only so the group membres will get by default access or not.
So, if a user is not part of the ownership group and passes the user criteria, will still not be able to access the knowledge article.
- 1,023 Views

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Do you know if there is a workaround for this? To apply some user criteria for the ability to contribute/edit articles if a user isn't a member of the ownership group?

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Unfortunately, no workaround identified so far. Ownership group trumps all the access. Only knowledge base owner and admin are able to supersede ownership groups. It requires customization to change this behavior.