---
sourceDocument: Australia Platform Analytics
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/now-intelligence

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Define anonymization

# Define Task Mining anonymization {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Replace personally identifiable information with alias data to protect sensitive user information.

## Before you begin

Set the application scope to Task Mining core using the application picker.

Role required: sn_tm_core.power_user, sn_tm_core.admin

## About this task

Note:  
You can't add new anonymization configuration records.

## Procedure

1. Navigate to WorkspacesTask Mining Workspace.
2. Select the Configuration icon ![]().
3. Under Configuration, select Anonymization.
4. Select the anonymization configuration record that you want to modify.  
   The available records are:

   Event Field Replacement Value
   :   Determines the replacement term for any event fields when the replaced event filter is applied. The default value is BLOCKLISTED. For more information, see [Create event filters to capture or exclude activity](https://www.servicenow.com/docs/R_vwLopHT8K3kmC9hM53AA "Set up event filters before starting a Task Mining project to capture specific application activity or exclude sensitive data. If no filters are active, all activity is captured.").

   Minimum level of anonymization
   :   Determines at the system level the minimum available level of anonymization when setting up a Task Mining project. This value defines how users are identified for the project that you're creating. The default value is LOGIN NAME. The other possible values are
       INITIALS for the user's initials or ANONYMIZED CODE.
5. Modify the Value field.
6. Select Save.

*[\>]: and then