Data masking

FEATURE AVAILABILITY

Data masking is only available for certain users. Reach out to your Customer Success Manager to learn more.

Workato stores job history details data for every recipe step according to your data retention policy. However, in some cases, you may prefer to restrict other workspace collaborators with privileges to access job history data from viewing sensitive information, such as employee SSNs or birth dates.

Data masking enables you to hide sensitive data at the trigger and step levels, ensuring better control over job history visibility.

How does data masking affect data storage?

• Trigger and action steps
• Activity audit log

Trigger and action steps

When you enable data masking for a trigger or action step, Workato doesn't store or display input and output data for that step.

However, trigger event data, which is used to repeat jobs, is still stored. This data is separate from job history data.

Activity audit log

Workato excludes masked input and output data from the Activity audit log and doesn't stream it to your Audit log streaming destination.

To indicate the excluded data, Workato replaces the step data with a placeholder in the activity audit log.

Enable data masking

You can mask data for individual recipe steps. Workato hides both input and output data from the job history.

Complete the following steps to enable data masking:

1

Open a recipe in the recipe editor.

2

Hover over the trigger or recipe step and click the ••• (ellipsis).

3

Click the Mask data toggle to enable data masking for that specific step.

Enable data masking

Example

In the following example recipe (opens new window), data masking is enabled for the Salesforce New/updated account trigger:

Recipe with data masking enabled

Before enabling data masking, the trigger's input and output data appears on the job details page:

Job details before masking

However, after enabling data masking, the trigger's input and output data is hidden:

Job details after masking