Customer interactions with support teams can involve sharing sensitive information, such as email addresses, payment card details, or bank account numbers.
For example, a customer reporting an unauthorized transaction may include their account number and card details in a ticket. The support rep handling the request may need those details to verify the transaction, while other support reps in the department may not need access to them.
Making sensitive information visible to other support reps can put customer privacy at risk.
Content masking and redaction in Zoho Desk help organizations protect selected information in ticket conversations while retaining the ticket and its history. Organizations can enable the capability for selected departments and use profile permissions to control which support reps can mask, view, or permanently redact content.
Availability
Permission required
Support administrators and users with Manage Privacy Settings can configure content masking and redaction.
Understanding Content Masking and Redaction
Content masking and redaction allow support reps to protect sensitive information in individual ticket threads and comments without removing the entire conversation or ticket history.
Let’s take a closer look at how content masking and redaction work and when to use.
| Content masking
| Content redaction
|
Purpose
| Restricts visibility of sensitive information that is still needed.
| Removes sensitive information that must no longer be retained.
|
Data retention
| Data remains stored in Zoho Desk but is hidden in the ticket and API responses.
| Data is permanently erased from Zoho Desk.
|
Subsequent access
| Users with respective profile permission can unmask and view data temporarily. When a ticket is refreshed of reopened, the data is masked again.
| Cannot be viewed or restored after redaction.
|
Usage scenario
| Masking can be used when information is to be accessed only by authorized users to investigate or resolve a support request.
| Redaction can be done when information is no longer required to be accessible by anyone.
|
Impact on ticket history
| Retains the ticket and its conversation history, with selected information masked.
| Retains the ticket and its remaining conversation history, with selected data removed.
|
Example
| Masking customer account details while a transaction dispute is being investigated so only the support rep resolving the dispute has access to it.
| Once the dispute is resolved, the account details are no longer required and it can be redacted.
|
Note:
- Both masking and redaction are manual actions. Sensitive information is not detected automatically.
- Masking or redacting an occurrence applies to matching information only within the same thread or comment, not across other threads, comments, or tickets.
- The audit log captures content masking, viewing, unmasking, and redaction, along with who performed each action and when. Administrators can monitor these entries and investigate unexpected activities.
Benefits
- Prevents unauthorized access: Sensitive information is visible only to authorized users while the rest of the ticket remains accessible.
- Reduces sensitive-data retention: Information that is no longer needed is permanently removed, reducing data breach risks.
- Preserves ticket history: Even though sensitive details are protected, the ticket and remaining conversation history are retained.
- Prevents accidental disclosure: Masked information remains hidden in quoted replies and forwards to prevent it from being shared by mistake.
- Supports accountability: Sensitive-content actions are recorded in audit log so administrators can review when required.
Business scenarios
Processing a refund request with payment details
A customer raises a refund request and shares their card details. Only the billing team needs access to this information to process the refund. Once the refund is processed, the billing team can use content redaction to remove the card details permanently, as they are no longer required.
This helps prevent retention of sensitive customer information and reduces the risk of data exposure.
Protecting account information during an internal escalation
A support rep adds a private comment containing customer account information for the senior manager to review. Only the senior manager needs access to these details and not the other support reps. The support rep can use content masking to restrict access to the selected information while keeping the rest of the comment visible. By masking the content, sensitive account information is protected while preserving the context needed for collaboration.
Responding to a personal-data removal request
A customer closes their account and requests the removal of personal information shared in an earlier support conversation. Administrator or support reps with Content Redaction permission can permanently remove the relevant details without deleting all the ticket history.
The service provided to the customer is retained for future reference but the personal data is removed to protect customer privacy.
Configuring content masking and redaction
Admins must configure content masking and redaction separately for each department.
Content masking must be configured for departments that must limit access to sensitive information while retaining it.
Content redaction must be configured for departments that should remove information permanently.
To configure content masking for departments:
- Navigate to Setup > Security and Privacy > Masking and Redaction.
- In the Content Masking section, click Configure.
- Click Select Departments and choose the required departments.
- Click Enable in the confirmation window.

To configure content redaction for departments:
- Navigate to Setup > Security and Privacy > Masking and Redaction.
- In the Content Redaction section, click Configure.
- Click Select Departments and choose the required departments.
Click Enable in the confirmation window.
Configuring profile permissions
Enable the relevant permissions in user profiles to allow support reps to perform content masking and content redaction.
Content masking
- Mask Content: Allows users to mask selected information in a ticket thread or comment.
- Unmask Content: Allows users to unmask protected information.
- View Masked Content: Allows users to temporarily view masked information.

Content redaction - Allows users to permanently remove selected information from a ticket thread or comment.

Note: Content redaction must be assigned carefully as this action deletes data permanently.
To configure profile permissions:
- Navigate to Setup > User Management > Profiles.
- Open the required profile.
- Under Ticket Permissions, perform the following:
- Enable Content Masking and select Mask Content, Unmask Content, and View Masked Content as required.
- Enable Content Redaction if required.
Masking content in a ticket conversation
Sensitive information can be masked when that must be accessible only by the authorized access and not by everyone. On selecting a value to be masked, all the matching occurrences within the same thread or comment are also masked.
Note:
- A minimum of 3 and a maximum of 150 characters can be masked per selection.
- A maximum of 5 text can be masked at a time in a thread or comment.
Administrator and user profile with Mask Content, View Content, and Unmask Content permissions can perform the respective action.
To mask content:
- Open the required ticket.
- In the ticket detail view, click the More icon of the thread or comment containing the sensitive information.
- Click Mask Content.
- Select the information to mask.
- Click Mask.
- Click Mask in the confirmation box.
To view masked content
- Open the required ticket.
- In the ticket detail view, right-click on the masked content.
- Click View Content.
- Click View in the information to mask.
To unmask content
- Open the required ticket.
- In the ticket detail view, right-click on the masked content.
- Click UnMask Content.
- Click View in the information to mask.
Redacting content in a ticket conversation
Sensitive data can be removed permanently from the system using content redaction.
On selecting a value to be redacted, all the matching occurrences within the same thread or comment are also erased, while the ticket and its remaining conversation history are retained.
Alert: Before redacting an information, verify and confirm if that information is no longer required. This action cannot be undone,
To redact content:
- Open the required ticket.
- In the ticket detail view, click the More icon of the thread or comment containing the sensitive information.
- Click Redact Content.
- Select the information to redact.
- Click Redact.
- Review the permanent redaction message and check I understand this content can't be recovered.
- Click Redact.
