Insights Censorship Settings
WalkMe has created a security mechanism that allows you to prevent the collection of your users’ sensitive information. The censorship mechanism is performed entirely on the client side, meaning the censored information never even reaches the WalkMe servers.
How It Works
How to Access Censorship Settings
To access your current Censorship settings, please follow these steps:
- Log into your Insights account at insights.walkme.com
- In Production settings, switch to the necessary environment and click on Environment Settings
- In the Censorship & Privacy tab, you will see the following screen:
Censoring HTML Elements By ID or Class Attributes
Enter the ID or Class attribute names you would like to censor under Censor IDs or Censor class names respectively, and the sensitive elements containing these ID and/or class attributes will not be collected by Session Playback tracking.
As an alternative, you can add the class “wm-hide” to any element on your website to censor that element.
Understanding Element Censorship
To enable User Behavior analysis, WalkMe collects the following fields by default:
- The “name” attribute;
- The “title” attribute;
- Element text;
- Element value; and
- Element label.
If you are concerned that one or more of the above fields might contain sensitive user information, please censor the element(s) you are concerned about.
Understanding Password Field Censorship
Insights will never collect keystroke data inside password fields (inputs of type=”password”) and there is no way to change this behavior.
No Retroactive Censorship
Please note that, after applying any of the settings in this section, your chosen censorship settings will only apply to subsequently recorded sessions.
If you discover that you have recorded sensitive information prior to activating your desired settings, please contact WalkMe Support to help you resolve this issue.
To learn more about privacy settings and how to disable the collection of properties that might contain personally identifiable information (“PII”), please refer to this Insights Privacy Settings article.