Skip to main content
New Participant
Jul 24, 2026 9:05 PM UTC
1. New

Sensitive data Redaction and Data Masking for Moveworks Interaction data in Analytics

Related products:Analytics

Moveworks Analytics currently shows user inputs and bot responses in plain text. While this level of visibility is extremely helpful for developers investigating unexpected bot behavior or addressing negative user feedback, exposing raw conversation text can create privacy and compliance concerns.

Submitting this as a proposal to introduce native, configurable data redaction and masking capabilities within the Moveworks platform for raw interaction logs and analytics dashboards.

Suggested capabilities would include:

Built in regex based and AI driven entity detection to automatically identify and redact common sensitive information, such as salary details, performance ratings, and similar confidential data.

The ability for tenant administrators to define custom regex patterns, keywords, or rules tailored to their organization’s specific privacy and compliance requirements.

2 replies

Employee
Oct 19, 2026 10:29 AM UTC

Hi ​@ramapr1 , Thanks for highlighting this. 

We already have data redaction and masking available through Custom Views in Analytics.

To set one up, log into your Moveworks org and go to Analytics > AI Assistant Insights > Interactions table > Create View. Then provide a name and description, choose which columns to hide from the view, and select the users to share it with.


Once you’ve created the view, users can access it on their end. Note that non-Analytics admins need the “Custom Views User” (under Roles & Permissions > Bot Analytics) role to see custom views in Analytics.

Please let me know if this helps.

ramapr1Author
New Participant
Oct 19, 2026 3:48 PM UTC

Jishnu, Thanks for your response. 
We’re aware of masking option through custom views. However, what we’re actually looking for is the ability to apply sensitive data redaction and/or data masking to the core analytics data itself. Right now, outside of custom views, an admin/dev with access to Analytics experience in Moveworks portal can see all user and bot interaction data without any masking.

Same issue applies when analytics data is downloaded through the DataAPI, since everything comes through unmasked. So the real need is for control over masking/redaction at the core analytics layer and Data API. That way sensitive data is not exposed in raw form when an admin looks up analytics natively in Mw or accesses it through DataAPI.