Feature Requests

Feature Request Summary: Respect system editor preferences in Relay Manager ( $EDITOR support) Problem: Relay Manager currently defaults to using nano when editing configuration files. On systems where nano is not installed (common in minimal or hardened environments), this results in a failure to edit the config. Who’s Affected: System administrators running Relay Manager on minimal Linux distributions or environments where default editors (like nano ) are not installed or not desired. Impact & Context: Breaks expected workflows on systems without nano installed Forces admins to install additional packages they may not want Goes against common Linux conventions where tools respect the $EDITOR environment variable Creates friction for users maintaining clean or hardened systems Desired Outcome: Relay Manager respects the $EDITOR environment variable when launching config edits If $EDITOR is not set, optionally fall back to detecting available editors or prompting the user to choose Avoid requiring or installing a specific editor like nano by default This would align Relay Manager with standard Linux tooling behavior and improve compatibility across a wider range of environments.

In the education world, Chromebooks are used by students and, increasingly, by teachers. Is it possible to add CyberSight to the Chrome DNSFilter extension?

Our company is over 85% MacOS. There currently is no version of the roaming client that supports CyberSight for MacOS. You AI Assistant says there are no plans to release one. This feature would be very helpful on MacOS and if a competitor offers it when renewal comes up, we would probably switch vendors over this.

We're requesting the ability to approve or deny access to blocked domains directly from the email notifications generated by DNSFilter. Instead of logging into the dashboard, administrators should be able to click through from the notification email to quickly take action (e.g., add to allow list, keep blocked, or submit for review). Customer Value: This would streamline the workflow for IT/security teams by reducing the number of steps required to manage blocked domain requests. It also provides a faster response time for end-users while maintaining admin control and oversight.

Summary Allow administrators to log into the DNSFilter dashboard using passkeys instead of a username and password. Problem Dashboard authentication currently requires a password, paired with MFA through authenticator apps or email. Customers who prefer passwordless authentication cannot currently use passkeys for direct dashboard login. Requested Capability Allow passkey-based login to the DNSFilter dashboard (WebAuthn/FIDO2) Support passkeys stored in platforms such as Bitwarden, Apple iCloud Keychain, Windows Hello, or similar providers Maintain compatibility with existing SSO workflows, where authentication is handled by the identity provider Optionally support hardware security keys as an additional authentication method Customer Value Enables passwordless login for the DNSFilter dashboard Provides a more convenient authentication option for administrators Supports modern authentication methods already used by many password managers and devices

Ability to create a WARN page that does not block a category/site but instead shows a warning page reminding users of some caveat before going to the requested site. For example, before going to a Generative AI site, a page appears warning the user to NOT enter any business confidential, HIPAA, or other PII into AI. There would be a button on the page to acknowledge the warning and continue to the site.

It would be ideal to be able to toggle an "auto uninstall" per client and set a policy to remotely delete agent that doesn't check in within 30, 60 or 90 days. Our RMM auto installs DNSFilter so it is an easy re-add if needed. But this would help us keep our counts up to date.

Would it be possible to have a scheduled report that showed a summary of blocked pages visited (Site/Domain, Category) that could be drilled down by User/Roaming Client?

Have the ability for our finance team to log in to DNSFilter, but have their role be restricted to only the finance aspects of the portal.

Allow for a direct connection between DNSFilter and Entra (AzureAD) without the installation of a tool.