Skip to content

Getting Started with SenseOn Reveal: Unlocking the Power of Your Security Data

SenseOn Reveal integrates into your current SenseOn platform. It gives you intuitive tools to explore and analyse data.

Filter your dashboard by: IT Hygiene / Threat Hunting / All

Reveal dashboard filter options: IT Hygiene, Threat Hunting and All.

Finding and opening dashboards

When you open Reveal, it shows a landing page that lists the dashboards that are available to you. It does not open a dashboard immediately. The landing page has:

  • A Search dashboards box, to find a dashboard by name.
  • Category chips under the search box, to narrow the list to a category.
  • Your dashboards, in sections and shown as tiles. The sections are in this sequence:
    • Favourites (if you have favourites)
    • Governance & compliance (only if a governance dashboard is available to your tenant)
    • Security insights
    • Custom dashboards (the dashboards that your organisation created, only if you have any)

To open a dashboard, select its tile.

Favourites

Each dashboard tile has a star. To add the dashboard to your Favourites, select the star. To remove it, select the star again. Your favourite dashboards show in the Favourites section, at the top of the landing page and at the top of the navigation menu.

Opening a dashboard from any page

When you hover over the Reveal item in the main navigation, a menu opens. The menu has the same list of dashboards, the same search box and the same category chips. Thus, you can go to a dashboard from any page. You do not have to go back to the landing page first.

Returning to the landing page

When a dashboard is open, its title bar shows a Reveal › Dashboard breadcrumb. To go back to the landing page, select Reveal in the breadcrumb.

You cannot open a dashboard that is hidden, unknown, or removed. If you follow a link to one of these dashboards, Reveal also takes you back to the landing page. It does not open a different dashboard.

Creating and editing custom dashboards

Your organisation can build its own dashboards, in addition to the dashboards that SenseOn gives. Custom dashboards are available to all users in your organisation. They show in their own Custom dashboards section on the landing page and in the Reveal menu. This section comes after the sections with the dashboards that SenseOn ships. The section is hidden until your organisation creates a dashboard.

ℹ Who can do this: The Admin and Manager roles can create, edit and delete custom dashboards. Analysts can open and read custom dashboards, but they cannot create or change them. The JSON panel and the generated-query view of the editor stay Root-only. For information about what each role can do, refer to User Management.

Creating a dashboard

  1. Open Reveal to go to the landing page.
  2. Select Create new dashboard. An empty editor opens.
  3. Add a widget.
  4. Select the data source and the measure that you want the widget to show. A preview updates while you build the widget.
  5. To put the widget on the canvas, select Apply.
  6. To add more widgets, do steps 3 to 5 again.
  7. Arrange the widgets on the canvas.
  8. Select Save.
  9. In the save dialog, give the dashboard a name. You can also give it a description.
  10. Assign one or more Categories to the dashboard. Select a category that is already in use, or type a new category and press Enter. You can assign up to 10 categories, and each category can have up to 64 characters. The categories set the category chips that the dashboard shows under, on the landing page and in the Reveal menu.

Your saved dashboard then shows in the Custom dashboards section on the landing page and in the Reveal menu.

Editing or deleting a dashboard

Edit and Delete are available only on the dashboards that your organisation created. They are not available on the dashboards that SenseOn ships. The title bar of a custom dashboard shows that a user created it.

  • On the landing page or in the Reveal menu, open the menu of a custom dashboard tile. Then select Edit or Delete.
  • When a custom dashboard is open, use Edit or Delete in its title bar.

When you edit a dashboard, it opens again in the same editor. In the editor, you can add, change or remove widgets, and save your changes.

Calculated fields

The data source of a widget gives a fixed set of columns and measures. A calculated field makes a new column or measure from them, for one widget. It does not change the source. For example, you can break logins down by the hour of day when they occurred. You can also band a numeric column into ranges, or divide one count by another.

ℹ Availability: From platform 5.33, calculated fields are on for all tenants. On platform 5.32, they are off by default, and SenseOn can turn them on for your tenant. Like all other functions to author custom dashboards, they are available to the Admin and Manager roles.

A calculated field belongs to the widget that you add it on. Reveal saves the field with that widget. While you edit the dashboard, a widget that uses a calculated field shows a Computed marker next to its title.

Adding a calculated field

When you build or edit a widget, a Calculated fields section is under the data source. This section lists the fields that you added. Each field has Edit, Duplicate and Remove. If a widget uses a field, the field shows a "Used in" tag. You cannot remove the field until you take it off that channel.

  1. Select Add calculated field to open the recipe chooser. The recipe chooser lists the recipe types in "The recipes" section of this page, each with a one-line description.
  2. Select a recipe.
  3. Fill in the form of the recipe.
  4. Give the field a name.
  5. The field then shows in the column pickers of the widget: X-axis, split, group-by, category, measure or sort. The pickers that show it depend on whether the field produces a category or a measure.

You can also add a calculated field directly from a column picker. Each picker that accepts calculated fields has a New calculated field… entry at the top. The picker also lists the fields that you already made, above the columns of the source. A tag shows if each field is a calculated dimension or a calculated measure.

ℹ Note: You cannot use a calculated field in the Filters or Time controls. You also cannot click into a calculated field to cross-filter or drill down.

The recipes

Recipe Produces What it does
Date part A category Takes the hour of day, day of week, day of month or month from a date and time column. Thus, you can break a widget down by, for example, hour of day. Reveal calculates date parts in the time zone of the platform, not in your display time zone.
Bucket values A category Groups the values of a text column into named buckets. You list the values for each bucket and give the bucket a label. You also give a label to all other values. You can choose to ignore case.
Bucket ranges A category Bands a numeric column into ordered ranges. You set an upper limit and a label for each band, with the lowest band first. You also set a label for all values above the top band.
Filtered aggregate A measure Applies an aggregation (count, unique count, sum, average, minimum or maximum) to a column. The aggregation uses only the rows that meet the conditions that you set. An example is the number of cases where severity is High or Critical. You can join conditions so that all must match (AND) or any can match (OR).
Arithmetic A measure Combines two measures, or a measure and a fixed number, with add, subtract, multiply or divide. It can round the result to a set number of decimals. A division by zero shows no value, not an error.
JSON value A category or a measure Reads a single value from a column that holds a whole JSON object, such as the Unmapped column on the Logs View sources. Refer to Taking a value from a JSON column.

Taking a value from a JSON column

The JSON value recipe reads a single value from a column that holds a whole JSON object.

ℹ Availability: JSON value and the GCP Security Findings source in this section are available from platform 5.33. The other recipes are available from platform 5.32.

Some data sources keep their original payload as JSON in one column:

  • The six Logs View sources have an Unmapped column.
  • MS Directory Audit Logs and MS Graph Alerts have a Raw Data column.
  • GCP Security Findings has a Raw Alert column.

The usual field pickers do not show these columns, because a whole JSON object is not useful as a dimension on its own. Only the JSON value recipe reads them.

GCP Security Findings is also a new source in the Dashboard Lab. It is available on tenants with a Google Cloud integration. It contains findings from Google Cloud Security Command Center about threats, vulnerabilities and misconfigurations in your Google Cloud resources. Each finding has its Category, Severity, State and the resource that it concerns.

Each row is one update to a finding. Thus, to count findings, count unique Finding Name values. To see how findings change, chart them over time.

To add a JSON value field:

  1. While you build a widget, select Add calculated field.
  2. Select JSON value.
  3. Select the Column to read from.
  4. If the source uses more than one data source, also select a Data source. This is because Reveal samples the keys from one data source at a time.
  5. Select the key to read. Reveal samples recent rows and shows the keys of the column as a tree. Each key shows what it holds (text, a number, an object, or a list). It also shows the share of sampled rows that contain it. To see the keys in an object, open the object. To find a key by name, use the search box.
  6. Select how to use the field:
    • Group the chart by it uses the value as a dimension. Under Treat as, select how to read it: as Text, a Number or a Date and time. If the key holds a list, you can take its first item, its last item, or the number of items. You can also select the value for a row that does not have the key. The options are no value, empty text or 0.
    • Count, sum or average it uses the value as a measure. Select an Aggregate: count, unique count, sum, average, minimum or maximum.
  7. Select Add field to put the field on the widget. On the widget, you can put the field on an axis or use it as the measure. This is the same as for all other fields.

A short summary under the form describes the field, for example "Reads evidence › verdict from Raw Data as text."

ℹ Note: Reveal builds the key tree from a sample of recent rows. Thus, the shares in the tree come from that sample. It is possible that the tree does not list a key that occurs only rarely.

Building on another field

An Arithmetic field can use another calculated measure as one of its values, to one level only. The measure that it references cannot reference a further calculated field. You cannot remove a field that another field uses until no field references it. When you rename the field, the fields that use it update.

Calculated fields on any source

You can add calculated fields on any custom-dashboard data source, which includes the Cases and Dynamic Observations sources. Some columns on these sources hold coded categories, such as Case Severity, Case Status and Threat profile. You can use these columns in Bucket values and in Filtered aggregate conditions. There, you select from their labels, not from their codes.

Dashboards (a few examples)

Case Activity Overview

This section gives a summary of the actioned cases across your estate. It is useful to understand:

  • Work done by the SOC
  • The threat profile that your company faces
  • Any actions that wait for your attention

Available widgets in Case Activity Overview:

  • High priority cases over time
  • Escalated cases over time

    Escalated cases over time widget.

  • Risky Users

  • MITRE Tactics
  • Common processes found within high priority cases
  • Total Count Case by Case Severity
  • Number of high priority cases by status
  • Threat status of resolved high priority cases
  • Data transfer within high priority cases
  • Number of high priority cases by device type

Device and User Insights

This tab gives comprehensive visibility into your device ecosystem and user behaviours, with detailed risk metrics and anomaly detection. It highlights:

  • Health status and compliance levels across your estate
  • User activity patterns with flagged high-risk behaviours
  • Potential security vulnerabilities that must have immediate attention

Available widgets in Device and User Insights:

  • Operating Systems
  • Operating systems across the estate past week
  • Least commonly installed program versions

  • Least common startup items

    Least common startup items widget.

  • NTLM Failed Authentication Attempts

  • Failed Kerberos Authentication Attempts
  • Escalated cases by device user
  • File Sharing Programs
  • Vulnerable Potentially Unwanted Programs (PUPs) Installed
  • VPN Applications
  • Remote Access Tools
  • Risky Users
  • Files in Use Containing Passwords

Data Transfer Overview

This tab lets you visualise and analyse all data movement inside and outside your network perimeter. This intelligence helps you to:

  • Find unusual data transfer volumes or destinations in real time
  • Monitor sensitive data flows across geographic boundaries
  • Detect potential data exfiltration attempts through pattern recognition

Available widgets in Data Transfer Overview:

  • Total Daily Upload Volumes
  • Total Daily Download Volumes

    Total daily download volumes widget.

  • Data Transfer by Country (Destination Host)

    Data transfer by country (destination host) widget.

  • Devices downloading most data

  • Devices sending the most data
  • Users downloading most data
  • Users sending the most data
  • File Sharing Programs

AI Governance

The AI Governance dashboard shows the use of AI applications and services across your estate, by device and user. Reveal lists it under Governance & compliance, the first section on the Reveal landing page. It also shows under the IT Hygiene filter. It has four tabs:

  • Overview: the AI usage on your devices and network
  • Accounts: the seats that your organisation holds with AI providers
  • Detection: what content scanning finds in prompts that users send to AI services
  • Microsoft 365 Copilot: how your organisation uses Microsoft 365 Copilot, from the audit log of Microsoft

ℹ Beta: The AI Governance dashboard is available to all tenants, and it is in beta. Its header shows a Beta tag. When you hover over the tag, it shows "This feature is in beta. Features, availability and pricing may change before general release."

How SenseOn detects AI use

SenseOn uses three detection methods to find an AI application:

Detection method How it identifies an AI application Platforms
Network traffic The hostname that the device connects to over an encrypted (TLS) connection. All devices with the Universal Sensor
Running process The name of the process that runs on the device. All devices with the Universal Sensor
Installed app The software inventory of the device. Windows and macOS only, because Linux devices do not report software inventory

If a user uses an AI application only in a web browser, nothing is installed on the device. Thus, the Installed app method cannot see the application. The network traffic method can still see it.

Each usage widget on the Overview tab uses one detection method. An indicator in the header of the widget shows the method. To see the method and the AI applications that it can find at this time, hover over the indicator. The figures in that widget cover only what its method can see. The AI applications detected by detection method widget covers all three methods. The Accounts tab uses data from your AI providers, not these methods.

Which AI applications are covered

The dashboard recognises AI applications from a list that SenseOn maintains and examines. It does not flag an item only because the item looks like AI. The AI applications detected by detection method widget shows the current list. Select the widget to expand a table with one row for each application and one column for each detection method. A tick shows that the method identifies the application. This widget shows the detection coverage of SenseOn, not the activity in your estate.

Remember these points when you read the dashboard:

  • Tools not on the list do not appear. The dashboard does not count an AI tool that SenseOn does not recognise yet, even if your devices use it. If you want SenseOn to add a tool, ask the SenseOn SOC through the Support Hub.
  • New tools are not added retrospectively. SenseOn matches usage to AI applications when it summarises the data of each day. When SenseOn adds an application to the list, the application shows from the day that the update reaches your environment. The dashboard does not show earlier activity.
  • Usage history starts when the dashboard was enabled. The usage widgets cover the last 7 or 28 completed days. They cover only the time after SenseOn started to collect the data of the dashboard for your tenant.

The SenseOn SOC can run a hunt across your raw network and DNS records in Hunt Lab. This hunt is useful for a one-off look further back, or for a tool that is not on the list.

Why the figures differ from Microsoft Defender

If you also use Microsoft Defender for Cloud Apps, it usually reports more AI applications than SenseOn. The two products count in different ways:

  • Defender compares activity with the catalogue of Microsoft, which has several thousand cloud applications. SenseOn uses its shorter, curated list.
  • Defender can count a visit to a web page as use of an AI tool. This occurs if the page loads an embedded AI feature. Examples of these features are a chat widget or a text-to-speech widget. SenseOn counts connections to AI services, and AI applications that run or are installed on your devices.

For the widely used AI applications, the two products usually agree broadly. Most of the difference comes from tools that are not on the SenseOn list, and from embedded web widgets.

Overview tab

Widget What it shows Detection method
AI applications detected by detection method The AI applications that SenseOn can detect, and the methods that identify each one. All three
AI services reached The AI services that your devices reached over encrypted connections, ranked by the number of devices that reached each one. This data comes from network traffic. Thus, it includes services that your organisation has no account with. Network traffic
Top AI users Users, ranked by the number of connections that their devices made to AI services. Usernames are local operating system accounts. Thus, it is possible that they do not match the cloud or corporate identity of the person. Network traffic
Deliberate versus background AI use The devices that reach AI services each day. The widget splits them by the source of the traffic. The sources are a dedicated AI application, a browser, or AI features in other applications such as Microsoft Office. A device can show on more than one line. Thus, do not add the lines together. Network traffic
AI applications in use The AI applications that ran on your devices, ranked by the number of devices that ran them. The widget counts each device once for each application. Running process
Code pushed by AI applications The number of times that AI applications ran git push from the command line. This widget counts attempts, not successful pushes. It does not include editors and graphical clients that do not call git directly. Running process
AI applications installed The AI applications in the software inventory of your devices, ranked by the number of devices that they are installed on. Installed app
Data uploaded per AI service The data sent to each AI service, split by source: a browser or an installed application. The widget counts the data when a connection closes. Network traffic

SenseOn can find the application that generated AI traffic only on Windows devices. If SenseOn cannot attribute traffic, it shows the traffic as Unattributed. It does not hide the traffic.

Accounts tab

The Accounts tab reports the seats that your organisation holds with connected AI providers, such as Anthropic and OpenAI. A seat is one account that a person holds with one provider. Thus, a person with accounts at two providers counts as two seats. Use the tab to find unused seats that you can reclaim, and to review who holds admin access. It is an IT hygiene report, not a source of cases or detections.

The tiles have data only for the AI providers that you connected. If you have no Anthropic or OpenAI integration, the tab shows Connect an AI provider to see accounts, not its tiles. It also shows a Set up an integration button that opens Integrations. An integration counts in all statuses. Thus, a paused integration still shows the tiles. If a provider is connected but does not share usage data, Dormant seats can still be empty.

  • Seats by provider lists each seat on your enterprise account with each provider. This includes seats that nobody used in the last 28 completed days. It does not count personal accounts. Its columns are Seats held, Active, Dormant, Never used, Hold admin and What can we see.
  • Dormant seats lists the seats with no activity in the last 28 completed days. The seat that was unused for the longest time is first. If one person holds seats with more than one provider, that person can show more than once.
  • Seats with admin roles lists the seats that hold an administrative role with each provider. The role names are the words that each provider uses. These are admin roles at the AI provider, not the Admin role of SenseOn.

Providers share different data with SenseOn. Anthropic shares what people actually do in the product. OpenAI reports only when someone creates, changes or removes a seat. It never reports if a seat is in use. For that reason, Active, Dormant and Never used have values only for providers that share usage. Only those providers show in Dormant seats.

The What can we see column tells you what each provider shares. The Total row adds only the Seats held values. This is the one figure that all providers report in the same way.

Detection tab

The Detection tab reports what content scanning finds in the prompts that your users send to AI services. In this release, content scanning looks for secrets and credentials, such as passwords and API keys pasted into a prompt. Each finding names the rule that fired and where it fired. The dashboard never shows the prompt text.

For this tab, you must have an Anthropic (Claude) Enterprise or Microsoft 365 Copilot integration. Message scanning must be on in the settings of the integration. If one of these conditions is not true, the tab shows Turn on content scanning to see what it finds, not its tiles. It also shows a Set up an integration button that opens Integrations.

Counts start on the day that content scanning is enabled for your organisation. The tab does not show earlier activity. A short history shows that scanning is new, not that AI use is new. If a tile shows Nothing to report, content scanning raised no detection in that window.

Widget What it shows
Total AI findings Each finding that content scanning recorded in the last 28 days. The tile also shows the change over the most recent 14 days, compared with the 14 days before.
AI findings per day Findings recorded each day over the last 28 days.
Findings by type How the findings split by type. In this release, each type comes from the secrets and credentials rules.
Users with the most findings The users with the most findings. The tile identifies users by the email address of the account that is signed in to the AI service. Thus, one person can show under more than one address.
Latest AI cases The cases that content scanning raised, newest first. Each case shows the detection type that fired and the related user. To open a case, select its case ID.

Microsoft 365 Copilot tab

The Microsoft 365 Copilot tab shows how your organisation uses Microsoft 365 Copilot: who uses it, in which apps, and how often. The Overview tab uses the detection methods of SenseOn, but this tab is different. It reads the audit log of Microsoft through an Office 365 Management Activity integration.

All tiles except Paid seats cover the last 28 completed days. The tiles do not include today. Thus, the newest day that they show is yesterday. Counts start on the day that SenseOn started to receive this data from Microsoft, and the tab does not show earlier activity. The tab shows agents, and apps that read the Copilot conversations of people, separately from people. It never adds them to the totals for people.

The headline row across the top shows:

  • People using Copilot counts people who used Copilot at least once. It does not count agents and apps. A small sparkline along the bottom of the tile tracks daily active users.
  • Interactions by people counts the prompts that people typed into Copilot. It also shows the change over the most recent 14 completed days, compared with the 14 days before.
  • Actions by agents counts the actions that agents took, not people. The totals for people do not include these actions.
  • Paid seats shows purchased and assigned Copilot licences, as a Purchased figure and an Assigned figure.

The tiles under the headline row are:

Widget What it shows
Copilot by app Interactions by people in each Microsoft 365 app, ranked. The tile does not include agents.
Daily active Copilot users People who used Copilot each day over the last 28 completed days.
Copilot interactions Daily interactions, stacked by who made them: people, agents and Security Copilot.
Agent activity The actions that agents took, not actions that a person typed. The agents are Copilot Studio agents, automation agents, scheduled prompts and Security Copilot. There is one row for each kind of agent, not one row for each agent. Microsoft records each action under the person that the agent works for. Its columns are Agent, Operation, Actions and People acted for.
Top Copilot users People with the most Copilot interactions, ranked. The tile does not count agent actions.
Apps reading Copilot conversations The applications that read the Copilot conversations of people through the export API of Microsoft, such as data security tools or archive tools. The tile shows each reader. Its columns are App, Reads, Messages read and People covered.
Empty states

For this tab, you must have an Office 365 Management Activity integration. If you do not have one, the tab shows Connect Office 365 to see Copilot use, not its tiles. It also shows a Set up an integration button that opens Integrations.

The Paid seats tile has its own empty state. If no Microsoft licence rows arrived in the last three days, the tile shows Connect Microsoft 365 Copilot to see paid seats. It also shows a Set up the integration button that opens Integrations. The rest of the tab still shows its tiles.

Choosing a Microsoft 365 integration

When the tab shows its tiles, the first item in its filter bar is an integration menu. The menu opens on All integrations. It then lists each of your Office 365 Management Activity integrations by name. When you select an integration, all Copilot usage tiles on this tab show only that integration. This choice does not narrow Paid seats, because its licence data comes from a separate source. The menu is hidden while the tab shows its empty state.

If you go to a different tab while an integration is selected, your choice shows there as a chip with the name of the integration.

Producing an AI usage report

To report on AI use across your estate:

  1. Open Reveal.
  2. Under Governance & compliance, select AI Governance.
  3. Review the Overview tab. Top AI users and AI applications in use answer most questions about who uses which AI application.
  4. Use Download data as CSV on each widget that you want to include. For information about the content of the file, refer to Download widget data as CSV.

Each Overview usage widget covers only the AI applications on the SenseOn list, in its own time window, and with its own detection method. When you share figures, also give this information.

1 data, 2 views

Two view options are available for each widget: chart or table view.

Chart view of a widget. Table view of the same widget.

The chart period badge

Each chart that reads a time period shows that period on a badge next to its title. The badge has a clock icon. Thus, you can quickly see how far back in time the chart looks. Because the badge shows the period, chart titles and descriptions no longer repeat it.

A Reveal chart's period badge, a clock icon and period shown beside the chart title.

The badge gives the period that the chart covers, for example Last 7 days, Last 24 hours or Last 28 days. On data recorded by day, a one-day window shows Yesterday. This is because that data holds whole days that end at midnight. A chart with no time window shows All time. A chart that shows only the most recent snapshot of its data shows Latest. To see a short note about the period that the badge reads, hover over the badge or move to it with the keyboard.

If the data of a chart has no time of its own, the chart shows the present, and thus it has no badge. A chart with a named period, such as "yesterday" or "this month", a specific date, or a date range also has no badge. This is true even if the period sounds like one of these labels. The badge shows only rolling windows, such as Last 7 days. When you drill into a chart, the chart keeps its period. Thus, the badge does not change.

Changing a chart's aggregation, sort or time bucket

On a bar, column or line chart, if an axis has choices, its axis label is a button with a chevron. Select the button to open a menu. The menu marks the option that is in force. The menu that you get depends on the axis:

  • Aggregation, on the value axis, changes how the chart summarises the measure: Sum, Average, Minimum, Maximum, Count or Unique count. The menu lists only the aggregations that suit the measure.
  • Sort, on a category axis, sorts the chart by its values: Ascending or Descending.
  • Time bucket, on a time axis, changes the period that each point covers: Hourly, Daily, Weekly or Monthly. A time axis has this menu, not a sort menu, because you read a time series in time sequence.

When you select an option, the widget runs again with that change. The change applies to your current view of the widget. Reveal does not save it to the dashboard. If an axis label has no menu, that axis has no choices.

Case titles when breaking down by case

When you break down a widget by case, Reveal shows the Case Title of each case next to its Case ID. Thus, you can tell the cases apart, and you do not have to open each case.

  • In chart view (bar, column, stacked column and pie), the case title is the label of the category. The label is on the axis or the slice. When you hover over a bar, column or slice, the tooltip shows its Case ID under the title.
  • In table view, a Case Title column is directly after the Case ID column.
  • The CSV download agrees with the table, and thus it has both columns.

When you select a case, the action still uses its Case ID. Thus, drill-in, cross-filter and View case in Experience operate as before.

ℹ Not yet shown on every tenant. The default Reveal query path adds case titles. Some tenants have the Reveal backend query path enabled (a setting that SenseOn manages). These tenants do not show titles yet. On these tenants, a breakdown by case lists bare Case IDs as before, until that path also supports titles.

Paging through table rows

In table view, a widget shows its rows on pages. It does not scroll in the tile. If there is more than one page, a footer under the table shows Rows X to Y of N. The footer also has a pagination control to move between pages. A table that fits on one page does not show the row count or a pagination control.

On a dashboard, each tile puts as many rows on a page as its height allows. Thus, a taller tile shows more rows on each page. The pages change only the display. They change which rows are on screen, but not the source data, its sort order, or the filters that you applied.

Exploring the Other slice on pie charts

A pie chart can group its smaller categories into one Other slice. You can select that slice to expand it in place. The pie then shows the slices that Other grouped. A breadcrumb row also shows above the chart: All slices and then Other (N slices). To go back to the full pie, select All slices or the ✕ button next to it.

A long tail opens one level at a time. An Other slice can hold many slices of its own. When you expand it, the pie shows the largest of them and puts the other slices into a new Other slice. You can expand this slice again. Each level adds a crumb to the breadcrumb row, for example All slices › Other (996 slices) › Other (994 slices). To go back to an earlier level, select its crumb.

If one of your own categories has the name "Other", the breadcrumb shows Other (grouped) for the synthetic slice. This keeps the two slices apart.

Pie charts group only measures that you can add together. Some measures do not sum across categories, such as a unique count, an average, a minimum or a maximum. A pie of such a measure shows its categories without an Other slice.

When you expand the Other slice, only the display changes. The query, the table view and the CSV export do not change.

Paging through chart bars

In chart view, a bar or column chart shows its bars on pages, in the same way as the table view shows its rows. Each page holds as many bars as fit the chart, so that you can read every label. A stacked column chart pages by category. If there is more than one page, a footer under the chart shows X to Y of N. The footer also has the same pagination control as the table view, and a View all button. A chart that fits on one page shows no footer.

To see the distribution of all the bars, select View all. The chart then shows every bar on an automatic axis, with fewer labels. To go back to the page that you had open, select Paged.

A chart with a time axis, for example one bar for each day, shows all its bars without pages.

All pages use the same value axis, with a size that agrees with the largest bar of the chart. Thus, you can compare a later page directly with the first page. The pages change only the display. They change which bars are on screen, but not the source data, its sort order, or the filters that you applied. The table view and the CSV download still have all rows. When the widget runs again, for example after a drill or a cross-filter, it goes back to the first page.

Exploring the Other group on Sankey charts

A Sankey chart keeps its largest flows. It groups the other, smaller flows into one grey Other node on each side. Thus, the total volume in the chart does not change. When you hover over Other, it lists its largest grouped flows.

To expand the grouped flows in place, select an Other node. A breadcrumb row shows above the chart: All flows and then Other (N flows). To go back to the full chart, select All flows or the ✕ button next to it.

As with the Other slice of the pie chart, an expansion changes only the display. The query, the table view and the CSV export do not change.

When a chart shows only the first results

Each chart fetches up to a fixed maximum number of rows. If the data of a pie, bar, column or Sankey chart comes back at that maximum, there can be more rows than the chart fetched. Then a line shows under the description: Only the first N results are included. More exist.

This is most important where the chart groups a long tail. Its Other slice, Other node or paged bars then include only the rows that the chart fetched. They do not include the rows after the limit. The table view and the CSV download read the same fetched rows, and thus they have the same limit. To focus on the rows that you want, narrow the widget with a drill or a cross-filter.

A widget can ask for a set number of results in its own definition, such as a top 10 or bottom 10. Reveal does not flag this widget, because that cut is intentional.

KPI tiles

A KPI tile shows a single headline figure. If the tile has a time series, it shows the latest value with its period next to it, for example 184 in Sep 2026. A small sparkline of the series is under the value, along the bottom of the tile.

Under the value, the tile shows the change from the previous period as an arrow and a percentage. It also shows the period of the comparison, for example ↓ 13% vs Aug 2026 (212). The arrow and percentage are green if the change is good, and red if the change is bad. Each tile has its own rule: for most tiles an increase is good, but for a tile where lower is better, a decrease is good. If the value does not change, the tile shows No change.

A KPI tile without a time series shows the value on its own, with no period, change or sparkline.

Download widget data as CSV

Next to the chart and table view toggles, the controls for each widget include a Download data as CSV button (the download icon). When you select it, Reveal saves the current data for that widget as a CSV file.

The file contains all rows of the table view, not only the page on screen. It uses the same column sequence and the column names that the dashboard defines. The export includes all changes that you applied to the widget, such as a drill into a data point or a cross-filter. Thus, a drilled widget downloads its drilled data. A confirmation shows when the download starts.

The name of the file is senseon_reveal_<widget-title>_<period>-<time-zone>.csv. In this name, period is the period badge of the chart, and time-zone is the time zone that the chart uses for its times. Thus, a shared file tells you its period and the zone of its times. An example is senseon_reveal_mitre-tactics_last-30-days-europe-london.csv. If a chart has no period badge, the name does not include the period.

ℹ Note: When there is nothing to export, the button is greyed out. When you hover over it, it shows No data to download. For example, there is nothing to export while the widget refreshes its data, if it shows an error, or if it really has no rows.

Times and time zones

Reveal shows dates and times in your own time zone, which it gets from your browser. Thus, the times on a chart agree with your work day. Timestamps, time axes, tables and exports all use the same zone, with two exceptions:

  • If a chart uses data that is stored as daily UTC totals, it shows UTC days. Its period badge ends in (UTC) to tell you this.
  • Reveal calculates a Date part calculated field, such as hour of day, in the time zone of the platform. It does not use your display time zone.

When you share a Reveal dashboard, the link contains the time zone that you used. Thus, the person who opens the link sees the same times as you. If the time zone of that person is different, a notice shows under the dashboard title bar: Times are in Zone (offset), from the link. The notice also has a Use my time zone (your zone) button that changes the dashboard to the zone of that person.

If Reveal cannot recognise the time zone in a link, the notice is different. It shows The link's time zone was not recognised, so times are in your time zone, your zone. Reveal then shows the times in your own zone. A link that already has your own time zone shows no notice.

CSV downloads also contain the zone. The file name gives the time zone, and the period of the chart if the chart has a badge. For more information, refer to Download widget data as CSV.

Opening a case in Experience

Case Activity widgets such as Total Count Case by Case Severity count cases. They do not list them. Reveal treats the identifier of a case as an attribute. Thus, you can break a widget down by Case ID to change a count into the individual cases in it. You can then open any one of these cases.

To go from a case count to a single case:

  1. Select a data point on a Case Activity widget (for example, a severity bar) to open its data point menu.
  2. Select Break down.
  3. Select Case ID. The widget runs again as a list of the case IDs that make up that data point.
  4. Select a Case ID value to open its data point menu.
  5. Select View case in Experience.

View case in Experience opens that case in Experience. Experience filters to the selected case ID over all time, so that a fixed time window does not hide an older case. The item shows only on a Case ID value that has data. It does not show on a count of cases, or on an empty or Unknown value.