---
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


---

# Activity scoping

# Activity scoping {#ariaid-title1}

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

Custom activities run in their own scope, even if it is different from that of the
workflow.
Any script that runs inside a custom activity with a scope can only access outside
artifacts that are within the scope of that activity or artifacts that are configured to run
in any scope. Conversely, an outside artifact can only access the script inside that private
activity if the outside artifact is running in the same scope. Activities with public scopes
can interact with outside artifacts in any application scope.

You can use private activities as part of a workflow that has a public application scope.
These activities are protected from reaching outside of the workflow or from being reached
from outside the workflow. For details about setting application scoping for custom
activities, see the field description table for the appropriate [activity
template](https://www.servicenow.com/docs/access?context=c_ActivityDesignerComponents&version=australia&pubname=australia-integrate-applications&ft:locale=en-US).  
Hinweis:  
Custom activities uploaded to the ServiceNow Store must be configured as accessible to all application scopes.