What is Masked Display?
Masked Display allows Jodoo to automatically mask field values based on preset or custom masking rules when form records are viewed, exported, or printed. This helps prevent sensitive data exposure and improves data security.
You can also configure Allow viewing unmasked data to further control whether members can reveal the original field values.
When to Use Masked Display?
Masked Display can be used in scenarios such as:
Protecting customer and employee information: Mask sensitive information such as phone numbers, passport or ID numbers, Social Security numbers, and bank card numbers so that complete values are not exposed when records are viewed.
Protecting financial data: Mask bank account numbers, IBANs, tax identification numbers, and other sensitive information in expense reimbursement, payment requests, invoicing, and other financial processes.
Meeting compliance requirements: Help organizations protect personal, financial, and other sensitive information and meet internal privacy and data security requirements.
What Does It Look Like?
The following example shows how Masked Display works when data is masked by default and members are allowed to view unmasked data.
Take an employee directory as an example. Sensitive fields such as Phone Number are automatically masked when members view records. Members can reveal the original values when needed.
Members can also reveal all unmasked values in a column at once.
For example,click View Plaintext in the column header. All original names in the column will then be displayed without having to reveal them record by record.
Prerequisite
This is a paid advanced feature. For details, contact our Sales Team.
How to Set Masked Display?
Step 1 Supported Fields
Masked Display is supported for the Single Line and Number fields.
Notes:
Subfields of the above field types in a Subform do not support Masked Display.
For fields with Masked Display enabled, we recommend that you do not use them as the Data Title, condition fields in Field Display Rules, Brief fields in workflows, Grouping Fields in views, fields assigned values through Custom Buttons, or other fields used for similar purposes.
Step 2 Access
Go to the form design page and select the field you want to mask.
In Field Properties > Field Security, tick Masked Display to configure the masking settings.
Step 3 Setting Masking Rules
Jodoo provides preset masking rules and also supports custom masking rules.
Preset Rules
Rule | Masking Method | Example |
Full Masking | Replace all characters with |
|
Custom Masking Rules
1. Creating a Custom Masking Rule
If none of the preset rules meets your needs, click Add Custom Masking Rule to create a custom masking rule. Configure the following settings:
Setting | Description |
Rule Name | Enter a name for the custom rule so that it can be easily identified. |
Number of leading characters to keep | Set the number of unmasked characters to keep from the beginning of the value. |
Number of trailing characters to keep | Set the number of unmasked characters to keep from the end of the value. |
Replace all other characters with * | Replace all characters other than the retained characters with |
Masked Character Length | For Mask Length, you can choose how many For example, suppose the original value is The following options are supported:
|
Masking Test | Under Masking Test, enter sample data and click Mask to preview the masked result. Click Unmasked to switch back to the original value and verify whether the rule works as expected. |
Notes:
Each field supports only one custom masking rule.
If the number of characters in the original value is less than or equal to the total number of characters configured to be kept at the start and end, the original value will be displayed without masking.
2. Editing a Custom Masking Rule
After a custom masking rule is created, you can edit it again. Click Edit to adjust settings such as the number of characters kept at the start or end and the mask length. After you save the changes, the masked display of the corresponding field will be updated accordingly.
Step 4 Testing the Masking Rule
After configuring a masking rule, click Preview Effect to check how the masked data will be displayed and verify whether the rule works as expected.
Enter sample data, then:
Click Masked to preview the masked value.
Click Plaintext to return to the original value.
Step 5 Allowing Members to View Unmasked Data
After Masked Display is configured, field values are displayed as masked data by default for all members. If members need to be able to reveal the original values, enable Allow Viewing Unmasked Data.
Enabled: All members can reveal unmasked data when viewing records.
Disabled: All members can only view masked values.
How to View Unmasked Data?
1. When viewing a record's details, click View Plaintext
to reveal the complete value.
2. When members view records in a view within their permission sets, they can reveal an entire column of unmasked values at once. For example, click View Plaintext in the column header to reveal all original values in that column.
Where Does Masked Display Take Effect?
Masked Display only takes effect in the scenarios described below. It does not take effect when editing records, processing workflow approvals, or using Data Factory, Aggregate Table, Automation Pro, dashboard charts, charts on pages, and other unsupported scenarios.
Operation | Where It Applies | Notes |
Viewing form records | Viewing records on the Data Details page, in views within permission sets, in Manage Data, when viewing source data in charts, in Query Data fields, Related Tabs, History, and other supported locations | 1. When searching or filtering records, members can use unmasked values to find matching records, but the field values in the results remain masked. 2. Masked Display is not supported when viewing records in Workflow Center > My Tasks or CC Me. |
Viewing workflow records | Viewing records in Workflow Center > Initiated and Processed | — |
Printing | Printing from a Data Details page or using Batch Print | Print/Export Results
|
Exporting | Exporting records from permission sets or Manage Data | Special Cases
|









