Responsive dashboard properties

  • Release version: Australia
  • Updated April 22, 2026
  • 2 minutes to read

    • Use properties to fine-tune dashboard behavior and appearance.

    Navigate to System Properties > Dashboard Properties to configure the main responsive dashboard properties. In the Filter navigator, enter sys_properties.list to configure other reporting properties.

    Responsive Dashboard properties

    Property Description

    Enables unified navigation under Platform Analytics and Platform Analytics Administration menu sections and common library pages for both Core UI and Next Experience analytics artifacts. Upon upgrade to Australia, this property is set to true by default.

    com.glide.par.unified_analytics.enabled
    • Type: true | false
    • Default value: true
    • Location: Add a system property to the System Property [sys_properties] table.

    When enabled, users see both Platform Analytics and Core UI (responsive) dashboards in the library. Users can still drill down to KPI details from responsive dashboard indicator visualizations.
    Enable fulfiller creation of Core UI dashboards

    com.snc.par.coreui.dashboard_create.enabled

    		 Allows fulfiller users to create Core UI dashboards after upgrade to Australia. There is a Create new button available in the Dashboards library with the option to create Core UI dashboards in the modal.
    • Type: true | false
    • Default value: true
    • Location: Add a system property to the System Property [sys_properties] table.

    Apply security rules to the list of users, user groups, and roles that are visible when sharing dashboards.

    glide.cms.dashboards.sharing_with_secure_search
    • Type: true | false
    • Default value: false
    • Location: System Properties > Dashboard Properties

    When enabled, the list of users, user groups, and roles that are visible in the sharing panel is restricted. The restriction is based on the configuration of the sys_user, sys_user_group, and sys_user_role ACLs. For more information, see Access control list rules.

    There is a performance penalty associated with enabling this property. Performance degradation may be based on the number and complexity of business rules and ACLs on your instance.

    Specify a comma-separated list of roles that can share their own dashboards.

    glide.cms.share_dashboards.role
    • Type: string
    • Default value: Empty

      When this property is empty, all users can share their own dashboards.

    • Location: System Properties > Dashboard Properties
    Note:
    Properties that restrict dashboard sharing do not apply to users with the admin and dashboard_admin roles. Users with these two roles can always share any dashboard.

    Maximum number of seconds for a widget to render on a responsive dashboard.

    glide.canvas.grid.widget_performance_threshold
    • Type: integer
    • Default value: none
    • Location: System Properties > Dashboard Properties

    For more information, see Optimize widget rendering time on responsive dashboards.

    Maximum number of widgets that can render simultaneously on a responsive dashboard.

    glide.canvas.grid.widget_render_concurrent_max
    • Type: integer
    • Default value: 3
    • Location: System Properties > Dashboard Properties

    For more information, see Optimize widget rendering time on responsive dashboards.

    Number of seconds that responsive dashboard widgets are cached in the browser.

    glide.canvas.grid.widget_cache_ttl
    • Type: integer
    • Default value: 2
    • Location: System Properties > Dashboard Properties
    Number of users, groups, and roles returned when searching for a name in the Share panel of a Responsive Dashboard.

    The value of this property is per category, so the default value of 100 may yield 300 results - 100 users, 100 groups, and 100 roles.

    glide.cms.dashboards.sharing.search.maxRecords
    • Type: integer
    • Default value: 100
    • Location: Add a system property to the System Property [sys_properties] table.

    Setting the value too low can cause the expected results not to be found. The minimum value is 5. Setting the value too high can cause performance issues.