Feature Requests

Enable support for assigning unique Bypass PINs per user or per device, rather than using a single global PIN across all clients. For organizations managing diverse environments with varying levels of access, having granular PIN control would improve both usability and security. Requested Functionality: Ability to configure unique Bypass PINs per user, per device, or per group Option to manage and audit PIN usage from the dashboard Support for PIN expiration or reset policies (optional for enhanced security)

Android works fine with work profile – work browser is logged via dns filter – but private profile browsing is not, It differentiate the Web Traffic. IOS doesn't work similarly. IOS logs both work and personal profile traffic in DNSFilter Dashboard.

iPad Roaming Clients get the Site Secret Key from the installed Config Profile. When changing fleets of devices from one site to the other the Roaming Client App does not automatically recognize the new site secret key from the newly deployed profile, in most cases a reinstall of the app is needed. This is cumbersome, lots of effort, and unsafe. Wouldn't it make more sense for the App to continuously check the site key? Same could apply for macOS when that client is also configured with a profile in the future.

Support the Local Domain feature for the iOS roaming client - https://help.dnsfilter.com/hc/en-us/articles/1500008108422-Roaming-Clients .

At this time in order to use the iOS Roaming Client, it needs to be on a device that is in supervised mode using an MDM. Requesting ability to use DNSFilter iOS Roaming Client on Unsupervised devices (in a BYOD scenario for companies wishing to extend the DNSFilter protections to personal devices).