---
schema_version: "1"
id: 9c7bf16167d8544c2dd6902f239a0d09eda0c6818ae3c20b1347b5ddd90a54f5
title: Create a Dynamic Data Masking Policy for Structured Data in Data 360
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_dynamic_data_masking_policy.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_dynamic_data_masking_policy.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 57109e5af8ed6b680d48190fc1fbe90233031065899f0261dcd1328fe03421af
description: Protect sensitive information by restricting data visibility based on user roles and permissions.
products:
  - Data 360
release: "264"
---
# Create a Dynamic Data Masking Policy for Structured Data in Data 360

Protect sensitive information by restricting data visibility based on user roles and permissions.

### Required Editions

Before You Begin

Review these important considerations to ensure your masking policies work as expected.

- If a field used in a data graph is governed by a masking policy, users can’t access this data graph.
- If a Boolean field is masked, the value is always displayed as False, regardless of the field’s actual value.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>All Editions</strong> supported by Data 360. See <a href="https://help.salesforce.com/s/articleView?id=data.c360_a_dc_editions.htm&amp;release=264.0.0&amp;type=5" title="Data 360 is available in several supported Salesforce editions. Some Data 360 features also require additional licenses.">Data 360 edition availability</a>.</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:left;vertical-align:top;" id="d214689e80">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d214689e80 ">To create a dynamic data masking policy:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d214689e80 ">
              <p>Permission set: </p>
              <ul>
                <li>Data Cloud Architect</li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

1. In Data Cloud, go to the Data Governance tab.
2. In the left pane, click **Policies**.
3. Click **New**, select **Dynamic Data Masking**, and click **Next**.
4. In Policy Builder, enter a unique policy name, and an optional description.
    
    The policy API name is auto-filled based on your policy name, but you can change it.
5. Click **Next**.
6. Select **Rules**, and select the resources to protect. In the **Resource** dropdown, select **Field in Structured Data**.
    
    By default, the rule applies across all data spaces. As new data spaces are added, these rules apply to their resources.
7. To restrict policies to specific data space scopes, click **Customize Scope**, deselect **Apply to the resources in all Data Spaces in Data Cloud**, and select the desired data spaces.
8. Click **Save**.
9. Select the action you want to take on the resource. From the Action dropdown, select **Mask**.
10. Select one of the following masking methods.
    
    - Redaction - Replace masked characters with X. Select the number of characters to redact.
    - Nullification - Replace data with NULL.
    - Datetime Rounding - Simplify date and time display by showing only the year or the year and month.
    - Numeric Rounding - Round numbers to the nearest whole number or the specified decimal places.
11. Define the conditions when this action must take place. For example, set a condition to trigger the rule if the **Financial Data.Account Info** tag is present in the object. Or, if the **Personal Data.Digital Identifier.Browsing History** tag is not present in the object.
12. To add more conditions, click **Add Condition**.
13. To group your conditions into different sets, click **Add Group**. You can use the OR operator to take action when any group meets the rule conditions.
14. Click **Save and Activate**.