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


---

# Virtual Agent secure password inputs

# Virtual Agent secure password inputs {#ariaid-title1}

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

The Include a password input toggle switch on the Action utility properties sheet lets you enter passwords securely for use in Virtual Agent conversations.
If the workflow discovers a password2 type as an input, the Action utility properties sheet displays the Include a password input toggle switch.  
Hinweis:  
In previous releases, inputs with a string data type would also display this toggle switch. Starting with the San Diego release, only password2 data types are supported. If you have existing actions that use password inputs, update them to use password2.  
Abbildung : 1. Input mapping ![Include a password input toggle switch.]()  
If you enable this toggle switch, you see messages about clients that are supported, along with fields that let you do the following:

* Designate the field you want to make secure
* Enter the text you want to use for the password-related prompt
* Enter the text for a confirmation prompt
* Enter the text to use for messages about channels that aren't secure
{#va-secure-inputs__ul_e22_sgy_b4b}  
Wichtig:  
To implement secure (password2) inputs in your Virtual Agent custom control, you must adhere to the scoped application requirements in Workflow Studio. For details, see [Workflow Studio scoped application requirements for secure inputs](https://servicenow-prod.fluidtopics.net/u5pEp9bSvncLFbvsgjiIgQ "Adhere to the following scoped application requirements to implement secure (password2) inputs in your Virtual Agent topics.").  
Abbildung : 2. Password detail fields

These password input type fields are dynamic in the sense that the fields you see map to the fields set for the action when it was created in Workflow Studio. Some of the password2 fields may also be read-only.

For password-related design considerations in Workflow Studio, see [Password (2 Way Encrypted) design considerations](https://www.servicenow.com/docs/access?context=password-2-data&version=australia&pubname=australia-build-workflows&ft:locale=en-US) .  
Note the following points about how password-related inputs are handled securely:

* Only users can see the passwords. No one else can.
* The passwords are held in memory on the server and are passed securely to the Workflow Studio Action or Subflow.
* When users enter a password on a channel, users can toggle the Hide text icon ![Hide text icon.]() to show or hide the password.
* ServiceNow admins can mark a specific channel as secure. If topic authors attempt to include a channel that isn't marked as secure, a warning message appears.

  For more information about creating
  secure channels, see [Create a Virtual Agent conversational custom chat integration](https://servicenow-prod.fluidtopics.net/RvGIDxPYGfwV6PAwXmbb8w "Use the Custom Chat Configuration Integration Framework (CCCIF) to create a conversational custom chat integration to support third-party chat clients so they can connect to the Virtual Agent Chat Server (VACS).").
* Passwords are masked (not readable) in queues, tables, and logs.
{#va-secure-inputs__ul_drv_pvy_znb}