Configure block and notification pages

Use the Web > Policy Management > Block & Notification Pages page to view or edit block page text and notification messages for your account.

When a cloud policy denies access to a resource or needs to inform the user of an event, it can serve any configured notification page. There is a standard set of pages included with your web product, and you can either modify these to suit your needs, or add your own pages. You can then refer to the notification pages from any of your policies.

The pages are grouped for ease of navigation. Click a down arrow next to a group name to see a list of all the pages within that group. To see all available pages, click All.


	Note General notification pages that you create are listed under Custom. Custom AUP pages are listed under Acceptable Use Policy (a limited-availability feature that may not be enabled for your account). To delete a custom page, click the delete icon next to the page name. The delete icon is displayed only if the custom page is not used in any policies.

Click the name of a page to edit its contents.

To create a new notification page:

Click New Page for a new notification page or New AUP Page for a new Acceptable Use Policy page.

Enter a Name for the new page.

Enter a short Description of the page. This appears under the page name in the Block & Notification Pages list, and should clearly identify the purpose of the page to any administrator.

Click Save.

The Page Details page is displayed, with the name and description at the top. You can now edit the page as required.

For information about editing the content of a new or existing notification page, see Editing notification pages.

For additional information about AUP pages, see Acceptable use policy.

Default notification page settings

Use the Settings area to configure default options for your block and notification pages. You can override any of these settings for individual pages.

Default language

The default language for block and notification pages is English. You can change this by selecting a different language from the Default language drop-down list.

If you select a different default language and then click Save, your changes are immediately visible to end users. Ensure that you have saved pages in the new default language; if a page is not available in the new default language, the English page is displayed.


	Note The end user registration pages for secure form-based authentication are already available in the following languages: French, German, Italian, Dutch, Spanish, Simplified Chinese, and Japanese.

See Language support.

Default logo

By default, the logo displayed on the notification pages is the Forcepoint Web Security Cloud company logo. To change the logo:

Click Edit. The Default Logo popup window is displayed.

Select Custom images, and enter the URL of the image you want.

The image must be a JPEG, GIF, or PNG file. Click Verify Image to confirm the format and location of the image file.

Click OK. The new logo is displayed in the Settings area.

Click Save.


	Note If you choose to display a custom logo, we recommend that you host it on an HTTPS site. This ensures that your end users do not see warnings about unsecure elements on notification pages that use HTTPS, such as end-user registration and secure form authentication.

Default footer text

Any footer text that you specify appears at the bottom of each notification page. You may wish to use this area to provide contact information for end users.

To change the footer text:

Click Edit. The Footer Properties popup window is displayed.

Enter or edit text as required.

You can select all or part of your text and use the text formatting buttons to add bold, italic, color and other formatting. Hover over each text formatting button to see its function.

Click OK when done. The new footer text is displayed in the Settings area.

Click Save.

HTTPS notifications

To enable the cloud proxy to serve the correct notification page to the user for HTTPS sites - for example, a block page if the site is in a category that the end user is prevented from accessing, or the Pre-logon welcome page for authentication - you need a root certificate on each client machine that acts as a Certificate Authority for secure requests to the cloud proxy.

To install the root certificate for your end users and enable notification pages for HTTPS sites:

In the Settings area, click the root certificate link and download the certificate to a location on your network. You can then deploy the certificate manually, using your preferred distribution method

Once the certificate has been deployed, return to this page and mark Use certificate to serve notifications for HTTPS pages.

Click Save.