Feature Requests

I would love to see a click-through (override) option on the block page added as a configurable feature. As an organization, our goal is not only to protect users from malicious and risky content but also to educate and empower staff to make responsible decisions. In some scenarios we would like to warn and inform staff members rather than just blocking the website outright. As an example, for generative AI sites we could point them to our policy or guidance. Is this a feature that could be introduced?

The ability to provide more dynamic and informative messaging on their block pages, especially for support scenarios that vary based on time of day or user context. The current block page allows basic messaging, but it lacks the flexibility to display support-specific contact info or after-hours instructions that could improve the user experience. Requested Functionality: Option to add custom support instructions, including multiple contact options Ability to include time-based variations (e.g., one message during business hours, another after hours) Rich text or markdown support for formatting Optional inclusion of links or email buttons Customer Value: Improves end-user guidance, especially in regulated or support-sensitive environments Reduces IT support burden by preemptively answering common questions Offers a more branded, professional experience

I don't know if that would be technically possible, but it would be a great features to get the Hostname or the Username of the Roaming Client in the block page notice email.

Always shows default appearance even though block page is attached to site

When someone submits a whitelisting request, the email is sent from [email protected] . Since I have my email configured to route to our help desk system, this triggers an automatic response with a ticket number and details. As a result, your system generates a new request and sends it back to us via [email protected] , creating an unnecessary loop. To resolve this, I suggest using a non-reply email address, such as [email protected] , for outgoing whitelisting requests. This would prevent help desk systems from automatically responding and creating a feedback loop.

The Blocked Page's Network Status should be a clickable button that displays the organizations it is being used on. We currently have to go through every single organization to verify if that org is using a particular block page which is tedious.

It would be great if you could have Multiple Bypass passwords per policy. That way the passwords isn't shared. Then you can also see when a user needed to use it.

The ability to create a custom block page that will only block by a specific category. Meaning that when you create the block page, you would have the ability to select an option that would display the category you wish to block it on rather than creating multiple polices with different block pages.

Update filter policy to allow a user to specify a web service url. The url will be called when a block or threat is logged. The call will be a POST to the url which included information such as time, deployment, fqdn, category. This will allow the user to create customized reporting or alerting based on real time threat data.