Enate System Setup Requirements / Whitelisting
Technical requirements recommended as part of setting up your organisation to use an Enate instance.
Last updated
Technical requirements recommended as part of setting up your organisation to use an Enate instance.
Last updated
With Enate you've got access to enhanced tooltips, explainers and inline help, plus content to let you know about new features when they appear. In order for these overlay explainers to show correctly in enate, you'll need to ensure that your company's security policy is set up to allow for the information to display (some companies policies can block this kind of information as a default).
Enate uses 'Userpilot' technology for its inline helpers to show. UserPilot uses Web Sockets to send data to client machines and requires that these work through any web proxies or firewalls that are configured within the customer environment. We've previously seen issues with the UserPilot Web Socket connection where proxies have been configured to perform SSL inspection against all traffic in the environment.
UserPilot provides the following list of addresses whichit is recommended to be whitelisted in order for the inline helpers to show correctly:
wss://api.userpilot.io
wss://analytex.userpilot.io
wss://analytex-us.userpilot.io
wss://analytex-eu.userpilot.io
wss://analytex-in.userpilot.io
wss://reporting.userpilot.io
Additionally, Enate requires that the following addresses are whitelisted to serve Enate specific media embedded within UserPilot experiences:
For further information on UserPilot security setup requirements, please see the following link: https://docs.userpilot.com/article/152-faq-content-security-policy
Enate also uses some feature usage services to help us improve our software features based on how it's used. For this to work correctly, the following url should also be whitelisted:
