> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zenable.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Insights

> Triage proposed requirements and guardrails by scope or by person

## Overview

**Insights** is the triage queue for *proposed* changes — requirements and guardrails Zenable has recommended but that haven't been accepted yet. It helps you refine those recommendations to cut noise and uphold your standards, and it routes each recommendation to whoever should act on it.

The same work can be viewed through two lenses, toggled at the top of the page:

| Lens       | Groups recommendations by…                                                                          | Use it to answer                                    |
| ---------- | --------------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| **Scopes** | **Where** the work applies — a repo, path pattern, package, or the CLI (the recommendation's scope) | "What's outstanding in *this* part of my codebase?" |
| **People** | **Who** is responsible — the scope's owners plus anyone a recommendation is assigned to             | "What's on *this person's* plate?"                  |

Both lenses read the same underlying recommendations; switching the toggle only changes how they're grouped — it never changes the counts.

## Status cards

Three cards at the top summarize the whole tenant and act as filters. Click one to filter the cards below by that status (click again to clear):

| Card                       | Meaning                                                                                         |
| -------------------------- | ----------------------------------------------------------------------------------------------- |
| **Total**                  | Every open or pending recommendation across all scopes                                          |
| **Open**                   | Proposed recommendations not yet in an approval flow                                            |
| **Pending Human Approval** | Recommendations whose change is waiting on an [approval workflow](/approval-workflows) decision |

Recommendations that have been **resolved** (accepted or declined) leave the queue — Insights is a work list, not a history.

## Scopes

Each **scope** card shows the scope's name, its open / pending counts, and its **owners**. Open a card to see the linked recommendations, assign them, and triage each one.

### Owners

A scope can be owned by a [Group](/permissions). The group's current members surface as the scope's **owners**, so everyone can see who's accountable for a part of the codebase. Owners are set wherever a scope is created or edited — including the **Owners** picker in the scope edit form on the [Requirements → Scopes](/requirements-and-guardrails) tab — and changing the owning group takes effect immediately (membership is live; no re-approval).

### Quality score

Each recommendation carries a **quality score** (0–10) shown as a color-coded number in the recommendations table:

| Color | Range       | Meaning                                       |
| ----- | ----------- | --------------------------------------------- |
| Green | 7 and above | High-confidence, high-priority recommendation |
| Amber | 4–6.9       | Moderate confidence                           |
| Red   | Below 4     | Speculative; review before accepting          |

The table defaults to sorting by quality score descending so the most actionable work surfaces first. Click the column header to reverse the sort.

## People

The **People** lens inverts the same data: each card shows the recommendations owned by that person or group (through a scope they're an owner of) or that are directly assigned to them. Use the **Assigned to me** button to jump straight to your own queue.

Group rows appear alongside individual people. Each group card shows the group's member chips and aggregates all scopes the group owns; clicking a group row drills into the group's full responsibility view.

### Assignment

Within a scope you can assign individual recommendations to a teammate or a [Group](/permissions). Assigning to a group fans out to every member — the recommendation appears on each member's People card and in their per-person counts.

## View as a list

The **View as a list** link switches from the grouped card view to a flat, sortable table of every recommendation — handy when you'd rather scan or bulk-act across scopes instead of drilling in one scope at a time.

## Related

* [Requirements and Guardrails](/requirements-and-guardrails) — what recommendations propose, and the Scopes tab where owners are set
* [Approval Workflows](/approval-workflows) — how Pending Human Approval recommendations get decided
* [Permissions](/permissions) — Groups, which back scope ownership and group assignment