Overview
Widgets are the building blocks of your dashboards in Torii, allowing you to display and interact with key data in a highly customizable way. Each widget serves a specific function, helping you monitor important metrics, visualize trends, and create action items —all from a single dashboard view.
This guide will walk you the different widget types available, how you can customize them, and how to make the most of their capabilities.
Common Capabilities
- All widgets can be edited and adjusted to fit your organization's specific needs. You can only edit widgets in Edit mode.
- All widgets can be dragged by grabbing the widget and moving it anywhere in the dashboard.
- All widgets can be resized by grabbing the widget corner and dragging to expand or contract the widget.
- All widgets offer an ability to Explore the source data in greater depth via the "View Table" button. The table that opens acts like other tables in Torii - you can edit the columns & column order, change filters (this will affect the widget data) and even download the source data for further analysis.
- All widgets can be configured and customized to present the data you are interested in highlighting and monitoring via the "Edit" button.
- Exact configuration options depend on widget type, but the common ones are:
- Label - Determines the name of the widget.
- Data Source - Determines the data the widget refers to.
- Widget Type - Determines the widget type.
- Group by - Determines how the selected field data is grouped into categories.
- Aggregation - Determines how the data of the selected field is aggregates. Torii currently supports the following aggregations: Count, Sum, Average, Max, Min.
- Field/Fields - Determines what field(s) the widget will represent. Does not appear when the aggregation is set to "Count".
- Filter by - Determines what data will be included/excluded in the widget data calculation and presentation.
- Sort By - Determines how data is sorted visually, and, if only presenting partial data, determines which data is presented (based on whether the data is ordered in descending or ascending order).
- Max Groups/Entries Displayed - Determines how much data a widget will display (number of columns, groups, table entries etc.)
Types of Widgets
Torii currently supports the following widget types:
Metric Widgets
Purpose: Display key performance metrics in a simple, easy-to-read format.
Common Uses:
- Track main KPIs.
- Highlight outstanding issues or cases to investigate.
- Show at-a-glance bottom line.
Examples:
- Show number of employees / overall SaaS spend / active contracts value
- Track upcoming renewals / new apps discovered
- Track issues that should be investigated such as apps or contracts without owners, past users with licenses, closed apps with spend etc.
Pie Chart
Purpose: Displaying data as proportional segments of a circle to quickly understand the relative sizes of different categories in a dataset.
Common Uses:
- Easily compare category contribution to a relevant total.
- Grasp data distribution at a glance.
- Highlight dominant categories.
Examples:
- Showcase most common app discovery sources
- View distribution of app spend by department / app state, to highlight groups and uncover any anomalies.
- Show app offboarding configuration to make sure all important apps are covered
Bar Chart
Purpose: Displaying discrete categories and making direct comparisons between them.
Common Uses:
- Show over-time metrics to understand trends.
- Compare groups directly to find anomalies or redundancies
- Rank groups by performance metrics.
Examples:
- Investigate app discovery date or expense transaction date to understand trends.
- Compare app spend / count by tag, Departments by overall / average spend per user.
- Highlight problem areas such as apps with high spend and low usage
Table Widgets
Purpose: Displaying detailed data for metrics that require more than a number or image to convey.
Common Uses:
- Provide a full breakdown of data for users who need to see exact numbers and attributes.
- Shine a spotlight on data anomalies by comparing them side-by-side with in-line items.
- Show enough details on an action item to make make it actionable..
Examples:
- Highlight past users with app access or active licenses, and provide details on who to contact to remedy the situation.
- Showcase apps with expenses exceeding contract value to investigate further.
- Alert on upcoming contract renewals where more license purchases are required.