Skip to main content

Firewall settings

Configure your network security software to allow Emma Legal

Written by Pieter Buteneers

Overview

Emma Legal uses modern web technologies to provide a fast and responsive workspace. Some corporate network security solutions inspect, proxy, or modify HTTPS traffic to enforce security policies. In certain cases, these tools can interfere with modern web protocols and reduce the number of concurrent connections available to the Emma workspace, which may lead to slow loading times or parts of the application not working correctly.

If your organization uses tools such as Netskope, Zscaler, or similar secure web gateways, we recommend adding Emma Legal and all of its subdomains to the allow list and excluding them from HTTPS/SSL/TLS traffic inspection where possible.

Domains to allow

Please ask your IT or security team to add the following domain to the allow list:

*.emma.legal

This includes all Emma Legal services, such as:

  • app.emma.legal – Emma workspace

  • docs.emma.legal – Product documentation

  • Any other current or future Emma Legal subdomains

Do you use a web security or traffic inspection tool?

Many organizations deploy software that monitors or filters web traffic. You may see one of these applications installed on your computer, or your IT department may manage them centrally.

Common examples include:

Netskope

A cloud security platform that can inspect and proxy web traffic.

Documentation:

Zscaler Internet Access (ZIA)

A secure web gateway that can apply URL filtering and SSL/TLS inspection policies.

Documentation:

Other common enterprise web security solutions

- Palo Alto Prisma Access

- Cisco Secure Access

- Microsoft Defender for Cloud Apps

- Symantec/Broadcom Secure Web Gateway

- Forcepoint Secure Web Gateway

If your organization uses one of these solutions, please forward this article to your IT department and ask them to configure the Emma Legal domains accordingly.

Instructions for your IT department

Please configure your security solution to allow:

*.emma.legal

The preferred configuration is to exclude Emma Legal from HTTPS/SSL/TLS inspection, decryption, or traffic proxying where your security platform supports this.

Examples:

  • Netskope: Create an SSL decryption bypass or traffic steering exception for *.emma.legal.

  • Zscaler: Add *.emma.legal to the allow list or configure an SSL inspection rule with a "Do Not Inspect" policy.

The exact configuration steps depend on your organization's security setup and policies.

Symptoms of this issue

If Emma Legal is not properly allow-listed, users may experience:

  • Slow loading of pages or documents

  • Loading indicators that never complete

  • Sections of the interface appearing empty or not updating

  • General slowness despite a stable internet connection

Need help?

If your IT team needs additional information or if you continue to experience issues after allowing Emma Legal, please contact our support team at [email protected].

When contacting support, please include the name of your network security solution (for example Netskope or Zscaler) and any relevant error messages or screenshots.

Did this answer your question?