The Umbrella User Guide Developer Hub

Welcome to the Umbrella User Guide developer hub. You'll find comprehensive guides and documentation to help you start working with Umbrella User Guide as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Add a Web Content Category Setting

Content Categories organize websites into categories based on the type of information served by the site; for example, gambling or social networking or alcohol. You limit identity access to web sites by selecting categories to block.

Web content categories are URL-based. Such that a web policy would match to Online Communities, to Sports, and to Adult.

Add Setting

  1. Navigate to Policies > Policy Components > Content Categories and click Add.
  2. Give your Content Category list a good descriptive name and choose Web Policies.
  3. Select content categories to block and then click Save.
    For a list of all categories and a description for each, see Web Content Category Settings.
    Your new custom Content Category list is now available for selection when you add a Web policy.

Web Policy Versus DNS Policy Content Categories

Web content categories classify full URLs, whereas DNS content categories only classify at the domain-layer. This means that if a domain contains multiple types of content a DNS policy can only block what the domain was categorized at, irrespective of what other types of content might be served in that domain.

For example:

  • is categorized as Online Communities
  • is categorized as Sports
  • is categorized as Adult

A DNS policy configured to block Online Communities blocks the entire domain of, but even if it is configured to block Sports or Adult instead of Online Communities it does not block access to these underlying URLs. This is because DNS only works at the domain layer.

However, a Web policy configured to block Online Communities and Adult allows access to because of URL-layer classification. Therefore, when creating a blend of Web and DNS policies to be applied to the same set of identities, content settings are more granular when enforced by Web policies than DNS policies and because web content is served over the web protocol, it is more pertinent to enforce content settings with a Web policy than a DNS policy whenever possible.

Add a DNS Content Category Setting < Add a Web Content Category Setting > DNS Content Category Settings

Updated 2 months ago

Add a Web Content Category Setting

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.