Filter Rules: Display Dashboards by Redirecting Users and/or Groups
Confluence is the hub for all the information in your teams, the single source of truth that your colleagues rely on. It’s the perfect location to create dynamic dashboards with live information from Jira projects, incidents from Opsgenie or custom charts with insights from Jira Service Management service desks.
And this power comes with the great responsibility of providing Confluence users the right dashboard when they access to it. Dashboard Hub for Confluence provides the ability to define rules to filter which dashboard is shown to either all users or a specific set of users and/or groups. Thus, users are redirected to a dashboard or wiki page. These rules allow you to:
Replace the Confluence native dashboard with a custom one defined on a wiki page or by one of the dashboards created in Dashboard Hub.
Display unique dashboards for each team by defining filter rules for selected users and groups
And still have all the features of Dashboard Hub: +70 gadgets, custom charts, 10 integrations, dashboard restrictions, slideshow, external share…
Create a dashboard
Use a regular wiki page to create your dashboard, using macros to insert gadgets and metrics (with the Confluence Macro: dashboard, for example). With this option, you can use Confluence native mechanisms to create a specific layout and leverage the existing Confluence macros.
Create a dashboard with the main functionality of Dashboard Hub (refer to Getting Started with Dashboard Hub for further information).
Only Confluence admins can create filter rules. Go to the Dashboard Hub configuration, in the global admin section: Go to Browse > Confluence Admin > Dashboard Hub > Dashboard Filter Rules
The priority is used to determine the order the filter rules should be processed. The priority is only important if you define more than one filter rule. A lower value means a higher priority i.e., the rule with priority 1 has a higher priority than the rule with priority 2.
When you click + Add Rule you’ll access the rule creation dialog
Show content from
Which content to show as your dashboard. Choose one of the following options:
Select a dashboard to be the default global dashboard of Confluence.
Either the global site homepage configured in the general configuration of Confluence or the personal site homepage, if the user has configured one in his user settings. Note: The user's personal settings will override the global setting. Use this option to allow personal dashboards.
Any wiki page within your Confluence. Use this option to display a specific wiki page as dashboard instead of the default dashboard.
Remember, the Homepage allows you to configure the site home page to which users will be directed when they log in!
Show content as
Only available for Server and Data Center users, due to Confluence Cloud API limitations
Enable Show content always as dashboard to render wiki pages as dashboards as well, without edit button, comments, etc. Thus, if you enable this option, when you display a wiki page as a dashboard, you won’t see the interaction buttons (e.g., edit, star, watch, restrictions, share…) nor comments, removing all unnecessary elements for seeing a clean dashboard.
Show content to
You can restrict filter rules to all users or a specific set of users and/or groups. Choose All Users if you want the rule to apply to all users, or choose to Restrict to and define the users and/or groups to which the rule should be applied.
Note: A filter rule will be applied as long as the user meets at least one of the restrictions. If no filter rule matches or no filter rules are defined, the default dashboard of Confluence will be displayed.
Differences of the Data Center vs Cloud edition
In Cloud, the Wiki Homepage has to be configured manually by the admin, since it cannot be automatically retrieved
“Show Content As” is only available for Server and Data Center users, due to Confluence Cloud API limitations
In Cloud, the redirection is not as smooth as it is in Server and Data Center, due to Confluence Cloud API limitations