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?” |
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 Approval | Recommendations whose change is waiting on an approval workflow decision |
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. 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 tab — and changing the owning group takes effect immediately (membership is live; no re-approval).People
The People lens inverts the same data: each person card shows the recommendations they own (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.Assignment
Within a scope you can assign individual recommendations to a teammate. Assignment is lightweight metadata — it routes work without gating it, and it’s reflected immediately in the People lens.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 — what recommendations propose, and the Scopes tab where owners are set
- Approval Workflows — how Pending Approval recommendations get decided
- Permissions — Groups, which back scope ownership