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


---

# Workflow scope

# Workflow scope {#ariaid-title1}

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

Workflow application scope determines the access that an application has to the
information in a workflow, specifically to the data contained in the activities in that
workflow.

When a workflow is created, it inherits the application scope from the gear menu for the logged
in user. This scope cannot be changed in the Workflow Editor. When the workflow executes, it runs
in this scope and can only be called from a different application if the workflow's accessibility
setting permits access to all scopes (public). Otherwise, the workflow's application scope is
private to the application.  
Hinweis:  
Any script that is created in the Workflow Editor, such as an advanced script in an If activity, runs in the scope of the workflow. All core activities provided in the base system or for Orchestration run in the scope of the workflow.

Custom activities run in their own scope, even if it is different from that of the workflow.
The scope of a custom activity can be private or public. 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.  
Hinweis:  
Custom activities uploaded to the ServiceNow Store must be configured as accessible to all application scopes.

## Workflow scope restrictions {#ariaid-title2}

There are some restrictions to public and private application scopes.  
During runtime, publicly scoped workflows can access other application resources, as long as these resources are set to be accessible to all application scopes. Privately scoped workflows in a private application scope can only access resources private to its scope. Due to scope access boundaries, any privately scoped workflows that make calls out to other scoped resources fail with either an exception or a hung activity while waiting for returned results. This occurs when making calls to these common global resources:

* ECC queues
* Tasks
* Approvals
* Events
* SLA timers
* Timers
* Script includes
* Business rules
* Workflow APIs
{#c_WorkflowScopeRestrictions__ul_csz_h5r_2r}

As you design workflows, validate the visibility and accessibility of all resources prior to
deployment.

See [Application scope](https://www.servicenow.com/docs/access?context=c_ApplicationScope&version=australia&pubname=australia-application-development&ft:locale=en-US).

For
information on how to configure the scope for a workflow, see [Workflow properties](https://servicenow-prod.fluidtopics.net/xqVDsiGH7sMbLO8ghC0s6Q "In the properties of a workflow, you can configure settings such as its application scope, start conditions, schedule, inputs, stages, and run time metrics. You can also view information such as the workflow author, version, and history.").