Global Allow/Block
Any site added to the global allow policy will be completely bypassed from Securly's proxying and will not be scanned at all by Securly Filter. Likewise, any site added to the global block list will take precedence over your other policies and will remain blocked.
Note
Securly always allows/whitelists certain domains to ensure seamless web filtering.
Global Allow/Block list in Securly may not be the ideal choice when your goal is to block a domain while allowing access to specific full URLs. It can lead to unpredictable outcomes, particularly when trying to block a domain like sites.google.com while allowing access to sites.google.com/mysite. This can create confusion among users and administrators alike as it may inadvertently block necessary access or allow prohibited sites.
To effectively manage access, especially in situations like the example above, utilize the Allow/Block list of that specific policy instead of the global policy. This method provides a precise way to control access—where blocks can be prioritized or overridden by allows, eliminating the confusion caused by broad settings in the Global list. Learn more about global and policy-level allow/block settings.
Caution
Adding certain high-level domains to the Global Allow or Block lists may affect Securly's ability to filter content, monitor activity, and send alerts. View notable domains and their effects on being added to allow/block lists.
Clarification on Manual Transfer of Block/Allow Lists from GoGuardian:
While it is technically possible for Securly Support to manually import block and allow lists from other filters like GoGuardian into Securly Filter, this practice is generally not recommended.
Due to the selective proxy nature of Securly Filter, manually migrating these lists may lead to inconsistent filtering experiences and unintended consequences. Instead, it is advisable to create and configure filter policies specifically tailored to the functionalities of Securly Filter to ensure optimal performance and security.