---
sourceDocument: Australia Conversational Interfaces
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/conversational-interfaces

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Configure cross-scope access privileges

# Configure cross-scope access privileges for topic blocks and custom controls {#ariaid-title1}

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

Enable topic authors and developers to access Virtual Agent topic
blocks and custom controls from other scoped applications.

## Vorbereitungen

Role required: admin

## Warum und wann dieser Vorgang ausgeführt wird

Developers and topic authors may need to access [topic blocks](https://servicenow-prod.fluidtopics.net/8AWvvrgqyP35emA~twAzCg "Topic blocks are reusable components that you can create to run common tasks and conversational elements in Virtual Agent conversations. Topic blocks simplify the topic authoring and maintenance process by enabling you to reuse standard procedures or actions across conversation topics.") and [custom controls](https://servicenow-prod.fluidtopics.net/uqXCOUXuZrvqWRrP0she6A "Custom controls are components that ServiceNow developers can create for use in Virtual Agent topics or topic blocks. Such controls include sliders or video players. Custom controls complement the controls provided in Virtual Agent Designer.") created in other
application scopes. To give them access, define cross-scope privilege records for
the appropriate applications. For more information on cross-scope privileges, see
[Cross-scope privilege
record](https://www.servicenow.com/docs/access?context=c_CrossScopePrivilegeRecord&version=australia&pubname=australia-application-development&ft:locale=en-US).

## Prozedur

1. Activate the Virtual Agent conversation plugins for the applications that are the source and target scopes, for example the CSM (com.sn_csm.virtualagent) or ITSM Virtual Agent (com.snc.itsm.virtualagent) plugins.
2. Set your application scope (the Source scope requesting access) using the [application
   picker](https://www.servicenow.com/docs/access?context=c_ApplicationPicker&version=australia&pubname=australia-application-development&ft:locale=en-US).
3. Navigate to AllSystem ApplicationsApplication Cross-Scope Access and select New.
4. On the Cross scope privilege form, complete the following fields.  
   {#configure-cross-scope-privileges__table_omr_5hg_g4b__entry__2}

   | Field | Value |
   |-|-|
   | Source scope | Application requesting access to another application's resources. |
   | Target Scope | Application whose resources are being requested (the scope with the topic blocks or custom controls). |
   | Target Name | Name of the asset being requested: sys_cs_topic |
   | Target Type | Table |
   | Operation | Read |
   | Status | Authorization for this record: Allowed |
   [ ]

   {#configure-cross-scope-privileges__table_omr_5hg_g4b}
5. Select Submit.

## Ergebnisse

The cross-scope privilege is listed in the Cross scope privileges
\[sys_scope_privilege\] table. Topic authors or developers can access the topic blocks
or custom controls from the target scope.