Managing Public Views

In this section:

Public views allow you to publish information on the web and allow users to view reports and other information without having to log on. There are two types of public views:

The general and custom public views can be secured through the addition of web server security. To increase security for public views so that each public page has access to only the intended information, you can restrict public pages on HTML files that display the view. For details, see Creating Public and Group Views.

The information in each public view (general or custom) may not be relevant to every public user who connects to Dashboard. You may want to prohibit specific functionalities and control the information a public user can view by excluding the display of available domains from the general and custom public views. To manage access so users see only relevant information:

Top of page

Managing Library Access in a Public View

Dashboard public pages include static content retrieved from the Report Library repository. This eliminates the need for the public page to execute a report each time the page is viewed. This functionality is implemented by increasing the capabilities of the public user from within Dashboard.

If a Managed Reporting user, designated as a public user, has Library privileges, the Dashboard allows those privileges to be surfaced in a public view and also when a developer is building content pages for the public user.

A user who is designated as a public user must have Library privileges to view output. Library content is displayed on the public page only if the content is available to the public user. Dashboard works within the constraints applied to user access of reports and does not override any access limitations imposed by the Report Library.

The available Library content includes the Library tab as a content page and Library content added to a launch, output, or list block.