> ## Documentation Index > Fetch the complete documentation index at: https://docs.goguardian.com/llms.txt > Use this file to discover all available pages before exploring further. # Review Filtering Contexts > How device, network, and location context change which GoGuardian Admin filtering path applies. Filtering context is the combination of device state, network path, user targeting, and location that determines how GoGuardian Admin evaluates traffic. Use this concept when the same site behaves differently for different users, devices, or locations. ## Understand Why Filtering Context Matters The question is not only "what [filtering policy](/products/admin/filtering-policies) exists?" It is also "which filtering path is active right now?" That matters because Admin can evaluate traffic differently depending on: * Whether the device is managed or unmanaged * Whether the user is on campus or off campus * Whether the traffic is being handled through a device-based filtering path or [DNS filtering](/products/admin/dns-filtering) on the network * Whether agent awareness changes how managed devices interact with on-prem DNS filtering * Whether [YouTube filtering](/products/admin/youtube-filtering) is even available in the active filtering path ## Review Common Filtering Contexts * **Managed device context** for devices already filtered through your existing Admin deployment * **Out-of-school context** when off-campus behavior differs from the on-campus experience * **School-network DNS context** for BYOD, guest, and unmanaged devices, or for campus traffic generally * **Mixed context** when managed devices operate on networks that also use DNS filtering ## Ask These Questions First * Is this device managed by the district? * Is the device currently on the school network, a guest network, or off campus? * Is the traffic expected to be filtered by device assignment, network context, or both? * Should managed devices bypass DNS filtering on campus, or should both paths stay active? ## Identify Signs of the Wrong Context * The same user gets different results on and off campus * Guest devices filter correctly, but district-managed devices do not * A network-wide DNS change does not affect managed devices the way you expected * The site result makes sense only after you inspect the active network path GoGuardian publicly describes smart agent awareness as a way to let agent-filtered users bypass on-prem DNS filtering when you want to reduce redundant policy conflicts. ## Apply Filtering Context in Practice * Start with the exact device and network path * Identify whether the request should be treated as managed-device filtering, DNS filtering, or an off-campus path * Verify the expected behavior in that context before changing any broad policy or network setting * Use logs, Policy Checker, and network reporting together when the active context is unclear ## Resources Review how school-network filtering is designed and configured. Use this concept page when the issue is not only context but also overlapping policy behavior. Use this troubleshooting page when the active context should be DNS filtering but the result does not match.