---
sourceDocument: Xanadu Conversational Interfaces
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/conversational-interfaces

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Configuring Sensitive Data Handler

# Configuring Sensitive Data Handler {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Detect and mask sensitive information that is shared in Agent Chat or
Virtual Agent conversations.

## Before you begin

Activate the Sensitive Data Handler plugin (com.glide.sensitive_data_handling).

Role required: admin, virtual_agent_admin

## Procedure

1. Navigate to AllConversational InterfacesSettings.
2. Under Sensitive data detection, select View all.
3. Slide the Active toggle switch to enable sensitive data detection.
4. Select the appropriate conversation flow:  
   1. Requester to agent - detect and mask sensitive data entered by the requester in an Agent Chat conversation.
   2. Agent to requester - detect and mask sensitive data entered by the agent in an Agent Chat conversation.
   3. Requester to Virtual Agent - detect and mask sensitive data entered by the requester during a Virtual Agent conversation.

   {#ac-configure-sensitive-data-handling__ol_h2k_rgw_4rb}  
   Note:  
   You must select at least one conversation flow.
5. The Regular Expressions tab displays the existing expressions:  
   {#ac-configure-sensitive-data-handling__table_hzl_rk4_gsb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the regular expression. |
   | Regular Expression | Pattern that defines the expression. |
   | Number of characters to mask | Number of characters in the regular expression that are masked. |
   | Start masking from | Direction the regular expression is masked: left to right or right to left. |
   | Status | * Active - this expression is masked. * Inactive - this expression isn't masked. {#ac-configure-sensitive-data-handling__ul_izl_rk4_gsb} |
   | Order | Order in which the active regular expressions are analyzed against a message to determine if there are any matches. |
   [Table 1. Regular Expressions]

   {#ac-configure-sensitive-data-handling__table_hzl_rk4_gsb}
6. Either select an existing expression to modify or create a new regular expression by selecting New and filling in the fields.  
   {#ac-configure-sensitive-data-handling__table_xgy_cjs_gsb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the regular expression. |
   | Number of characters to mask | Number of characters in the regular expression that are masked. |
   | Masking symbol | Symbol used in place of the sensitive data. |
   | Status | * Active - this expression is masked. * Inactive - this expression isn't masked. {#ac-configure-sensitive-data-handling__ul_ath_hjs_gsb} |
   | Domain | Name of the domain that this regular expression affects. If you select Global, then the regular expression applies to both the agent and requester domains. For the agent and requester to see each other's domain, the administrator must do one of the following: * Include the domain where the regular expression should be visible as a child domain to the corresponding parent domain. * Grant necessary access to the appropriate domain if it's a sister domain. * Set the regular expression under a global domain. {#ac-configure-sensitive-data-handling__ul_ftq_5wh_hsb} |
   | Regular Expression | Pattern that defines the expression. Check your regular expression on a regex validation site such as <https://regex101.com/> |
   | Order | Order in which the active regular expressions are analyzed against a message to determine if there are any matches. |
   | Start masking from | Indicates whether the regular expression is processed from left to right or right to left. |
   [Table 2. Sensitive Data Regex form]

   {#ac-configure-sensitive-data-handling__table_xgy_cjs_gsb}
7. On the Agent system messages tab, enter information for the message that the agent sees if they enter sensitive data:  
   {#ac-configure-sensitive-data-handling__table_vhk_ggw_4rb__entry__2}

   | Field | Description |
   |-|-|
   | Description | Description of the system message. |
   | Value | Exact wording of the system message that displays to the agent. |
   | Updated | Date and time the message was most recently updated. |
   | Updated by | Name of the user who most recently updated the message. |
   [Table 3. Agent system messages]

   {#ac-configure-sensitive-data-handling__table_vhk_ggw_4rb}
8. On the Requester system messages tab, enter information for the message that the requester sees if they enter sensitive data:  
   {#ac-configure-sensitive-data-handling__table_hq2_kgw_4rb__entry__2}

   | Field | Description |
   |-|-|
   | Description | Description of the system message. |
   | Value | Exact wording of the system message that displays to the requester. |
   | Updated | Date and time the message was most recently updated. |
   | Updated by | Name of the user who most recently updated the message. |
   [Table 4. Requester system messages]

   {#ac-configure-sensitive-data-handling__table_hq2_kgw_4rb}
9. Select Save.

*[\>]: and then