Data Mask & Seed Requirements and Limitations
This topic provides the requirements and limitations that govern working with Data Mask & Seed. Before working with Data Mask & Seed, review these requirements and limitations.
Required Editions
| Available in: Lightning Experience |
| Available in: Professional, Enterprise, Unlimited, and Developer Editions with the Salesforce Data Mask add-on license. |
Requirements and Limitations
Before working with Data Mask & Seed, review the following requirements and limitations:
- Permissions and access
- Object masking constraints
- Custom library limits
- Masking job record and job concurrency caps
Permissions and Access
- To access and work with the new Data Mask & Seed application, assign users the
following Permission Set License and Permission Set. Make sure to assign the Permission
Set License before assigning the Permission Set:
- Data Mask And Seed User Permission Set License
- Data Mask and Seed User Permission Set
- To use the Create with Einstein option to generate custom library info entries, you must have Einstein enabled for your user, which requires your org to have an Einstein license. If your org has this license, either a Salesforce admin or you can enable Einstein for your user.
To enable Einstein for Data Mask & Seed:
- Verify that your org has an Einstein license.
- In the UI Setup menu, enter Data Mask in the Quick Find field.
- Select the Data Mask & Seed settings page.
- Enable Einstein for your user.
Object Masking
When you include the User object in a masking policy, Data Mask & Seed masks only Portal users (users of type = Portal).
Custom Libraries
When using Salesforce’s Einstein utility to generate info entries for custom libraries, each Einstein generation of info entries is limited to a maximum of 100 entries.
Masking Job Processing
Record Limits
- When a masking job exceeds 20,000,000 records, Data Mask & Seed runs the job without applying the Maintain Field Value Distribution feature.
- Per masking job, Data Mask & Seed supports masking a maximum of 350,000,000 records. When a job exceeds this limit, it's cancelled and an error message is recorded in the Masking Job Report.
Concurrency Limit
- Per sandbox, Data Mask & Seed supports running a maximum of 12 masking jobs during the current 24-hour rolling window. When a sandbox exceeds this limit, new jobs are cancelled and an error message is recorded in the Masking Job Report of each cancelled job.
Related Topics
After reviewing these Data Mask & Seed requirements and limitations, you can begin working with the app:
- To create and edit masking policies, see Create a Masking Policy and the Policies Tab
- To create and edit custom libraries, see Custom Libraries Overview
- Once you have created a masking policy that suits your masking needs, do any of the following:
- Manually run a masking job using that policy, see Run a Masking Job
- Schedule masking jobs to be automatically run using that policy, see Schedule a Masking Policy
- While a masking job is in progress or after the job completes, you can view the job's current status or review the completed job's results, see the Jobs Tab
