Whether you’re brand new to GoGuardian or a 1.0 veteran, there’s a lot to learn about filtering and policies in GoGuardian Admin 2.0. Let’s go over the basics!
Filtering in GoGuardian Admin is controlled by policies. Policies are a set of rules that control access to:
Click HERE to go over a step-by-step guide on how to create a policy.
Policies are applied by OU - you can apply a Policy to a particular child level OU, or apply the policy to a parent OU, whose child OUs will inherit the policy.
Click HERE for a step-by-step guide on how to apply policies to your OUs.
- Click to create a new custom Policy
- Policy card
- Policy name and description
- Click the pencil icon to edit the Policy
- Click the menu icon reveal the Delete Policy button
- Policy information
Admin 2.0 filtering introduces the ability to schedule filtering for particular IP ranges or times of the day. You can have different policies applied automatically during particular times of the day.
Click HERE for more on how to configure scheduled filtering for different off-site filtering options.
Testing your policies
Often times Admins want to see what exactly is going on from a user’s perspective - this is a great practice but can result in some undesirable situations regarding the test data for the user account. The best practice here would be to create a specific test user login that will not be tied to any actual users in your organization. Use your favorite actor, school mascot, or fictional character’s name to test your user experience and filtering policies. Do NOT use an account that already belongs to one of your users.
For more info on troubleshooting your filtering, click HERE
Policy Conflict Rules
Sometimes policies have conflicting rules. Let’s go over what happens in those scenarios. For reference, an applied policy is a policy that is directly added to an OU, and an inherited policy is applied to an OU’s parent OU. You can see the difference with a down arrow on the left side of the policy name at the apply policy page.
Applied policies take priority over inherited policies. Any conflicting settings are resolved with the applied policy's setting winning over the inherited setting for the same thing.
- Conflicts at the same level are resolved with Allow/On always winning over Block/Off.
- General rule: if your setting is more specific it should take priority over a general rule. i.e. A site that is allowed in Sites, but is blocked by a category should be allowed.
- Filter Apps, Filter Sites, and Filter YouTube toggles for enabling filtering are policy specific.
- Policy specific filters(including restrictions on age, sidebar, and comments) are only applied when the respective filter toggles are on for that policy.
- When there is a difference between the toggles in different applied policies under Apps & Extensions, Sites, Youtube, if the toggle is ever on, for any of the applied policies, then the toggle will be resolved as On throughout.
- In Youtube Filtering, the rank for policy rules from most general to most detailed is Keywords, Categories, Channels, Videos. So, barring other variables, a video that is whitelisted should be viewable no matter what the rules in Keywords, Categories, or Channels are.