Feature Requests

Admins should get an alert of unused allowlist entries to allow them to clean up the list for anything no longer necessary.

Ability to determine the date in which a Policy was Created.

Ability to filter the list of roaming client by entering in multiple roaming client ID's/Hostnames

Better Block Page Bypass Functionality (Multiple codes, expiration times, limited bypass access)

We should be able to give a site or agent a Policy, that policy should be able to just inherit another policy, using whole policy chain before it and over riding all prior policies - this allows us to do a BLOCK ALL (or strict default policy), and on a selective basis, allow more freedom - so in our example, we would want "WHITELIST ONLY" for the whole site, and then 3 in mission critical sites available for one policy + the whitelist only, then the second policy will be mission critical + whitelist, but would allow us to say trusted user, can access a few more less required sites

The ability to set a custom block page message instead of the default: "If you feel you've reached this page in error, please click here to notify the network administrator."

In the Manage Roaming Clients window, it would be very helpful to have a column for (last known) IP Address of the client. For us, we split our clients out into the multiple Sites we have, and we have to use a totally separate platform to view the IP address of the host to thereby identify what Site it belongs to (based on subnet), and then manually put it there.

We need a tool that allows you to enter a url such as: www.bet365.com and enter a user such as 'Joe Bloggs' to check if they would be blocked/not in this scenario.

As an admin, I would like the ability to stop users from uninstalling the DNSFilter macOS RC. This would be for users who have admin accounts on the computer.

It would be great if we could add a description to the collections as we create them and to have the ability to edit the description after a collection is created. We're manually managing our collections and providing some context in the form of a description as to what each collection is for (besides just the name) would be helpful seeing as there's a number of users helping to manage DNSFilter.