---
sourceDocument: Brazil Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Activate parallel jobs

# Activate parallel jobs for data anonymization {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Use parallel jobs to reduce your anonymization job execution time.

## Before you begin

Role required: admin

## Procedure

By default data class and user based anonymization jobs run using a single thread. Multiple threads may be activated for data class and user based jobs. In addition, federated jobs used during cloning uses parallel jobs with 3 workers by default.

1. In the navigation filter enter <kbd class="ph userinput">sys_properties.list</kbd>.
2. Create the property <kbd class="ph userinput">com.glide.data_privacy.max_parallel_workers</kbd>
3. **Optional:** To adjust the number of federated job parallel workers, edit the <kbd class="ph userinput">dp.max_concurrent_clone_item_workers</kbd> property.
4. Verify the Type is integer.
5. Important:  
   It is recommended to start with a small number of workers per node(2 or 3).
   Enter the number of parallel job workers in the Value field up to 5.
{#parallel-jobs-anonymization__steps_ofq_kc5_dcc}

