When creating a device, you can choose up to two profiles that are enforced on the device. When you query a device that enforced 2 profiles, the rule engine will look for a match in the first profile. A match means:
- Filter was triggered that blocked something
- Service rule was triggered that blocked, redirected or bypassed something
- Custom rule was triggered that blocked, redirected or bypassed something
- Default Rule was triggered that blocked or redirected something
If the first profile didn't match any rule, and Default Rule is set to BYPASS mode, meaning it will resolve the requested domain from authoritative DNS, this is when the 2nd enforced profile is consulted. The rule engine will then perform the same flow as above and look for a match.
If you have a business account, you can also leverage the Global Profile feature within any Sub-Organization. This can add a 3rd layer, meaning you can enforce up to 3 Profiles on any Device.
- The first linked profile must be set to Default Rule → BYPASS. In all other cases (block or redirect), the rule engine will never consult your 2nd profile as the Default Rule will match every query.
- You cannot create schedules for devices that have multiple profiles.
There are many powerful behaviors that you can accomplish with this feature. Some of these include:
You may have multiple profiles, but they probably have few/many rules that are common between all of them. If you change a rule in one, you have to go and manually change it in all other profiles. Instead, you can just have a single “Global Profile” that has all your common rules. Then your device specific profiles can have only the rules you need on those specific devices. So you can have something like this:
- Device A: Everyone Profile → Work Profile
- Device B: Everyone Profile → Home Profile
- Device C: Everyone Profile → Employee Profile
“Everyone Profile” contains things you probably want on all devices (block Malware, Ads, Phishing), while device/use-case specific profiles can only contain rules for things you only need on those specific devices. This eliminates the need to duplicate or sync rules.
If you have a business account, and leverage sub-organizations you can make this 3 tiered:
- Device A: Global Profile For Entire Org → Support Department Profile → User Specific Profile
- Device B: Global Profile For Entire Org → Marketing Department Profile → User Specific Profile
- Device C: Global Profile For Entire Org → User Specific Profile
The rule engine within a single profile works as follows:
- Custom rules take precedence over everything
- Service rules are second in line, and are checked if there are no custom rules that match the DNS query
- Filters (which block things) are 3rd in-line and will match a domain if there is no overriding custom rule or Service rule
- Last in line is the Default Rule, which will, like the name suggests, match queries that aren't affected by any of the above
If you wanted to have a Service Rule supersede a Custom Rule, you cannot do this within a single profile, as custom rules always get matched first. However you can accomplish this by adding a second profile, where your Service rule exists in the first profile, and a custom rule in the 2nd profile. This way, the Service rule will always be looked at first, and if nothing matches, then the custom rules from your 2nd profile will be looked at next (provided no custom rules in your first profile matched anything).
Updated 4 months ago