Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Managing the visibility of insights

Updated on October 29, 2021

Control which insights are accessible to other users of your application by setting specific visibility options. For example, as an application administrator, you can make your insights available for use on landing pages by exposing the insights as public visibility.

Before you begin: Add the Explore Data page to your application. For more information, see Organizing the main navigation for a portal.
Note: You can add the Explore Data page only if your application uses a Cosmos React or Theme Cosmos in hybrid mode.
  1. In the navigation pane of your application, click Explore Data.
  2. In the Insights section, click the insight whose visibility you want to edit.
  3. Specify the visibility of the insight:
    ChoicesActions
    Manage the visibility of list-based insights
    1. In the upper-right corner of the screen, click ActionsInsight details.
    2. In the Insight details modal dialog box, in the Visibility list, select who can see your insight.
      For example: Select Shared to share the insight with your access group.
    Manage the visibility of chart-based insights
    1. In the upper-right corner of the screen, click Edit.
    2. In the upper-right corner of the screen, click ActionsInsight details.
    3. In the Insight details modal dialog box, in the Visibility list, select who can see your insight.
  4. Optional: To give the chart a supplementary title, select the Show title check box, and customize the title.
    For example: In the Title alignment list, display the chart title in the center by selecting Center.
  5. Click Submit.
For example: You can verify the visibility of all insights by accessing Explore Data.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us