Advanced Security: Whitelist and Blacklist

Admins can control access to the helpdesk by using whitelists and blacklists to filter users by domain name, IP address, email address or language. These filters apply to user actions such as logging in, registering, and creating tickets (via email or the web).

The IP, email and domain lists are checked on every request, not only at sign-in: in the browser, through API keys, AI assistants connected through MCP, and the chat widget. Someone who is signed in when a list starts refusing them is signed out and told why. A refused API or MCP call gets 403 with the code ip_not_allowed or email_not_allowed.

Whitelist

Use a whitelist to explicitly allow access from trusted sources.

This is helpful when you want to restrict access to employees without needing to pre-create their user accounts. Any domain or IP not on the whitelist will be denied access.

Blacklisting

Use a blacklist to block unwanted access.

For example, if the help desk is for business customers only, admins can blacklist public email domains like gmail.com or hotmail.com. Users from those domains won't be able to submit tickets, register, or log in.

The account administration sidebar with the settings cog highlighted, opening the Security Configuration page.

Adding a blacklist or whitelist

Admins can follow these steps to control who can access the help desk:

  1. Go to Account administration > Account > Security
  2. Scroll down to White & blacklists
  3. Click on the desired tab. Below are the available options:
    • Domain names
    • IP Addresses
    • IP Addresses For Staff (checked for agents and above, in addition to the IP Addresses list)
    • Email Addresses
    • Languages
  4. Click on the + icon
  5. Enter the value that needs to be added to the whitelist or blacklist, and hit enter. Repeat as needed
  6. Click save

Note: Both whitelist and blacklist can be used at the same time. When determining which are allowed or blocked, the blacklist always overrides the whitelist.

Misconfigured whitelists can lock out legitimate users. Always test with a non-admin account after changes.