---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Scoped knowledge bases

# Scoped knowledge bases {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

To protect knowledge bases containing sensitive articles, use a scoped knowledge base.
Even system administrators and knowledge administrators can't administer scoped knowledge bases
unless explicitly authorized through user criteria.

For example, say you have a knowledge article with sensitive payroll information that should be
seen only by the Payroll department and not by a system administrator or knowledge administrator.
You could create a knowledge article with the sensitive information in a scoped knowledge base
within the Human Resources: Core application.  
Only users with the admin role of an application and the knowledge_admin role can administer a scoped knowledge base. You control access to knowledge bases of an application with application administration enabled, such as HR, through the ACLs of the knowledge tables in the application instead of global ACLs. To define access to a scoped knowledge base, specify appropriate user criteria for users, including system administrators and knowledge administrators.  
Hinweis:  
For Scope Master tables to derive scope and execute scoped ACLS, you must set the glide.enforce_security_scope.\<scope_name\> system property to true.

You can't modify the scope of existing knowledge bases. They remain in the global scope.
However, you can create a scoped knowledge base to protect sensitive knowledge articles.

To create a scoped knowledge base for an application, in addition to the knowledge_admin or
admin role, you must have access to view and select that application in the application picker
(see [Application picker](https://www.servicenow.com/docs/access?context=c_ApplicationPicker&version=australia&pubname=australia-application-development&ft:locale=en-US)). For example, before you create a knowledge base in the Human
Resources: Core application, you must select the Human Resources: Core application in the
application picker, and then create the knowledge base. Then, when you create a knowledge base,
on the Knowledge base form, the application scope of the knowledge base is set in the
Application field.
**Zugehörige Tasks**   

* [Create a knowledge base](https://servicenow-prod.fluidtopics.net/Pfz2BpgL6Wor91Lbq6wyog "Create a knowledge base to provide a self-service platform for users to store, share, and manage content. Configure knowledge bases into product or service categories and manage user access based on permissions. Customize workflows for publishing and retiring articles in the knowledge base.")
* [Control access at the knowledge base level through user criteria](https://servicenow-prod.fluidtopics.net/18Bpf5hjqjam1xnFX8zg7Q "You specify user criteria for a knowledge base to control which users are granted access to read and contribute knowledge articles to that knowledge base.")  
**Zugehörige Informationen**   

* [Select an application from the application picker](https://www.servicenow.com/docs/access?context=t_SelectAnAppFromTheAppPicker&version=australia&pubname=australia-platform-administration&ft:locale=en-US)
* [Application administration](https://www.servicenow.com/docs/access?context=application-administration&version=australia&pubname=australia-application-development&ft:locale=en-US)