---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Configure a data privacy job

# Configure a data privacy job {#ariaid-title1}

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

Configure a data privacy job on your production instance to use anonymized data on
your non-production instance for user and data class jobs.

## Vorbereitungen

The data privacy job supports two de-identification use cases:

* Sensitive data of specific sys_users
* Sensitive data of particular data class.
{#config-data-privacy-job__ul_dds_vyn_4tb}

Role required: data_privacy_processor and admin

## Prozedur

1. Elevate to the data_privacy_processor role.  
   For details on role elevation, see [Elevate to a privileged
   role](https://servicenow-prod.fluidtopics.net/QSMW4UNBg6bevZDKAPGT2Q "The base system admin can elevate to a privileged role to have access to the features of High Security Settings.").
2. Navigate to System SecurityData PrivacyData Privacy Job.
3. In the Data Privacy Jobs list, click New.
4. In the form, fill in the fields.  
   {#config-data-privacy-job__table_tgp_2pb_grb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the job. |
   | Description | Description of the job. |
   | Privacy Configuration | The privacy policy configuration to use for this job. For detail on Privacy policy configurations, see [Create a data privacy policy](https://servicenow-prod.fluidtopics.net/C3Xr6RL~Ez53k3vAm7J1RA "Configure a data privacy policy to specify which data privacy techniques are used when anonymizing your data."). |
   | Frequency | * Run Once: The job will run once in the specified time window. * Weekly: The job will run each day of the Day of the week field in the specified time window. * Monthly: The job will run each day of month as entered in the Day of the month field in the specified time window. {#config-data-privacy-job__ul_dxs_r2h_cgc} |
   | Users | Select the users or group of users to be anonymized in this job. Up to 1000 users of a group can be processed. Hinweis: This field displays only when the selected privacy policy condition requires a selection of user records. |
   | Dry Run | Run the job as a test. No records are affected when running this job. Results are displayed in the Summary field as though the job had executed. Hinweis: Dry Run must be turned off when configuring a data privacy job with rollback. See [Roll back a data privacy job](https://servicenow-prod.fluidtopics.net/YbwNMFAfe2MJXb6WFtLTrg "Roll back a data privacy job on your non-production instance that uses anonymized data from your production instance to a state prior to de-identification of a data class or user job.") for details. |
   | State | State of the data privacy job: * Completed: Job completed successfully. * Ready to Schedule: Default state for new jobs. * Rollback in progress: The job has been set to roll back anonymization. * Rollback complete: The anonymization job rollback has successfully completed. * Completed with Errors: The job completed but has errors. See [Data Privacy Job Logs](https://servicenow-prod.fluidtopics.net/aC5haAg1QDJ5X4mRqdTcNQ "Review errors from Data Privacy jobs.") for more information. * Error: Job did not complete and had an error. See [Data Privacy Job Logs](https://servicenow-prod.fluidtopics.net/aC5haAg1QDJ5X4mRqdTcNQ "Review errors from Data Privacy jobs.") for more information {#config-data-privacy-job__ul_lpq_zyh_htb}A read-only field. |
   | Estimated record count | The estimated number of records this job affects. A read-only field. |
   | Summary | A read-only field that displays the results of the job when you execute it. |
   | Time window start | The start of the time window to run this job. The job will run after the time entered in this field. A valid time value is in Coordinated Universal Time based on a 24 hour time notation. |
   | Time window end | The end of the time window to run this job. The job runs before the time entered in this field. If the job has not yet completed, the job will pause and resume at the next time window start. The end time must be after the start time. A valid time value is in Coordinated Universal Time based on a 24 hour time notation. |
   [Tabelle : 1. Data privacy job fields]

   {#config-data-privacy-job__table_tgp_2pb_grb}
5. Right-click the form header and select Save from the context menu.  
   After saving the record, the Schedule Job and Delete Job buttons appear.
6. Click Schedule Job to run your job.  
   The job runs between the times selected in the Time window start and Time window end fields. If the job has not completed during the start and end time window, the job will continue at the next time window start.  
   Hinweis:  
   A job can only be executed once, even if Dry Run is selected. To run the same job again, create a data privacy job using the same field values.
7. **Wahlweise:** Choose one of the following functions:  
   * Cancel Job: Cancels the data privacy job.
   * Pause: Pauses job and rollback recording, if rollback has been selected. A warning message will display after a three-day expiry period for rollback contexts. See [Roll back a data privacy job](https://servicenow-prod.fluidtopics.net/YbwNMFAfe2MJXb6WFtLTrg "Roll back a data privacy job on your non-production instance that uses anonymized data from your production instance to a state prior to de-identification of a data class or user job.") for details.
   * Resume: Restarts a paused job. Rollback is not supported for resumed jobs if paused. Cancel the job and create a data privacy job. The recording uses an unexpired rollback context.
   {#config-data-privacy-job__ul_hw2_zll_ltb}