> ## Documentation Index
> Fetch the complete documentation index at: https://docs.caplena.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Insights Radar
> Surface AI-generated findings automatically inside your reports and review them all in one project-level list.
**Insights Radar** are findings that Caplena generates automatically from your report views and surfaces in a side rail next to your report. Use them to spot shifts, drivers, and noteworthy patterns without having to ask Agent each time you open a report. You can also add your own insights manually to capture observations alongside the AI-generated ones.
Insights Radar and [Tasks](/insight-and-reports/insights-and-tasks/tasks) are closely connected: an insight surfaces a finding, and a task turns it into assigned, trackable follow-up work. See [How Insights and Tasks work together](/insight-and-reports/insights-and-tasks/tasks#how-insights-and-tasks-work-together) for the full picture.
## Turning on Insights Radar
Insights Radar is enabled per report view.
During the introductory period (until 31 December 2026), Insights Radar is **automatically enabled for frequently used report views**. You can change the update frequency or turn it off for any view using the steps below.
Open your report, click the **pencil icon** in the top-right corner, and select **Bulk edit view settings**.
In the **Insights updates** column, open the dropdown next to the view you want and choose **Daily**, **Weekly**, or **Bi-weekly**. Views set to **Off** don't generate insights.
Click **Done**. Insights are generated automatically for the view from then on.
The **Insights updates** column header shows your organization's run budget (for example, **60 of 60**). See [Limits](#limits) for how runs are counted.
Only standard insight elements generate insights. [Custom Insight Elements](/insight-and-reports/insight-elements/custom-insight-elements) don't.
## Where you see Insights Radar
* **Report side rail** — a collapsible panel on the right of any report view, shown as collapsed badges or expanded card stacks. The rail header shows the total insight count and the date of the most recent activity.
* **Per insight element** — each insight element can have multiple insights, accessible via the chip on its upper-right side. When an element has related Insights Radar entries, a small sparkles button appears; hover or click it to see those insights in a popover, then open one to expand the rail directly to that card.
* **Insights board** — a dedicated project-level page where you can browse every insight across all report views, grouped by view or by project.
Insights Radar is scoped to a saved report view. If you change filters or segments away from the view's saved configuration, the rail is disabled until you reset back to the saved view.
Anyone who can see a report view can also see its insights and linked tasks.
## The Insight lifecycle
Every insight goes through three stages:
1. **Discovery** — on a regular interval (for example, weekly), Agent looks for interesting findings across your reports. If it finds something worth showing, an insight is created and shown in the report. If it doesn't find anything noteworthy, nothing is shown.
2. **Updates** — on the same regular interval, live insights are rechecked and refreshed with the latest data, so the numbers stay current for as long as they remain relevant.
3. **Retirement** — once an insight is no longer relevant, it's retired and removed from the view. A new insight can spawn later if the underlying data starts shifting again.
For example, in an NPS report: for as long as the score stays relatively constant, no insight is shown. If the NPS moves, an insight is created highlighting the change and its likely drivers. It keeps refreshing on the regular schedule as long as the shift remains meaningful. Once the score stabilizes, the insight is retired.
You can also dismiss an insight yourself at any time, regardless of where it is in its lifecycle. If a task is linked to an insight and **auto-close** is enabled on that task, the task closes automatically when the insight is dismissed or retired — see [Auto-close](/insight-and-reports/insights-and-tasks/tasks#the-task-detail-page).
## Reading an insight card
Each Insights Radar card includes:
* **Title** — short summary of what was found.
* **Sentiment** — a smiley showing whether the finding is positive, neutral, or negative.
* **Body** — markdown-formatted explanation, often with supporting numbers or topic references.
* **Chips** — metadata tags such as the source insight element, the public ID, whether the insight is outdated, and whether it was created by a user or by Caplena.
* **Actions menu** (burger icon, top-right of the card) — ask Agent a follow-up question about this insight, open the insight's detail page, [create a task from it](/insight-and-reports/insights-and-tasks/tasks#creating-a-task-from-an-insight), archive it, or dismiss it.
Dismissed insights are hidden from the rail and the count, but remain available in the project-level list if you filter for them.
## Notifications
You get a notification in your Caplena inbox when a new insight or task is created, and whenever an existing insight or task changes. You can also have these notifications delivered by email, Slack, or Microsoft Teams.
### Configuring notification settings
Go to **Settings → Notifications** to choose which insight and task events reach you outside the Caplena inbox, how often, and on which channels.
The settings are shown as a table with two groups, **Insights** and **Tasks**. Click a group to expand it and see its notification types:
| Group | Notification types |
| - | - |
| Insights | New, updated, outdated, archived |
| Tasks | Task assigned, due soon, closed |
For each notification type, you set:
* **Channels**: Select the **Email**, **Slack**, and **Teams** checkboxes to choose where the notification is delivered.
* **Frequency**: Choose **Instant**, **Daily**, or **Weekly**. Choose **Inbox only** (off) to keep the notification in your Caplena inbox without sending it to any other channel.
The group row applies a channel or frequency to every type in the group at once. A partially filled checkbox or a dashed frequency pill means the types in that group have different settings.
Slack and Teams must be connected before you can select them. If a channel isn't connected, click **Connect** next to its column header to open the integration setup.
#### Presets
Use the presets above the table to fill in the whole table at once:
| Preset | What it does |
| - | - |
| **Quiet** | Turns off all insight and task notifications. You still see them in your Caplena inbox. |
| **Balanced** | Sends key events only: new insights by daily email, updated insights by weekly email, assigned tasks daily by email and Slack, and tasks due soon by daily email. Outdated and archived insights and closed tasks are off. |
| **Everything** | Sends every notification type instantly on email, Slack, and Teams. |
| **Custom** | Selected automatically when you change individual settings so they no longer match a preset. You can't select it directly. |
Start with a preset, then adjust individual rows. Caplena saves each change immediately.
## Adding a manual insight
Insights aren't only created automatically — you can add your own:
1. Open the report and go into **Configure View** mode.
2. Click **Add Insight**.
3. Choose **Manual**, give it a title and a description.
4. Save it.
Your insight appears in the rail alongside AI-generated ones, marked as user-created so it's clear who authored it.
Manual insights are useful for pinning analyst commentary, decisions made in review meetings, or context that the AI doesn't have access to (for example, a known data quality caveat).
## Archiving an insight
From **Configure View** mode, open the burger menu on an insight and select **Archive**. Archived insights are removed from the active rail but aren't deleted — you can find and unarchive them later from the Insights board by filtering for **Archive status**.
## Disabled state: filters or segments diverge from the view
Insights Radar is tied to the saved configuration of a report view. When you change the report's filters or segments so that they no longer match the saved view, the rail is disabled and the button shows a popover explaining why. Click **Reset** in the popover to restore the view's saved filters and segments and re-enable the rail.
## Limits
During the **introductory period**, which runs until **31 December 2026**, the Enterprise, Team, and Agency plans include **60 insight runs per organization**. A run checks a view for new insights and updates existing ones, which can also retire insights that are no longer relevant.
You decide how to spread the 60 runs across your views. For example, you can update one view frequently or several views less often. More views and higher frequencies use up runs faster.
A run is only counted when something has changed. If the underlying data, the report, and the view all stay the same (no new rows, no added insight elements, no changed filters), no run is deducted.
**No cost during the introductory period.** Insights Radar is free to use until 31 December 2026. Nothing will be billed automatically when the introductory period ends.
## Related
* [Tasks](/insight-and-reports/insights-and-tasks/tasks) — turn an insight into assigned, trackable follow-up work.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.