# Impact Dashboard

Where leadership focus turns into accountable ownership.

The KPIs from [KPI Dashboard](/user-guides/impact-dashboard/kpi-dashboard.md) become named, owned, actionable assessments here — and the same delegation flow IT uses is available to every manager and Application Owner. Same data, distributed accountability.

Instead of *"we have N inactive users"* sitting on IT's plate, the dashboard reports *"manager X owns 5, manager Y owns 3, app owner Z owns 2 — all delegated, all clocking notifications."*

It is designed to answer simple but important questions:

* Where in our organisation does each problem actually live?
* Who is the right person to own and fix each finding?
* How do I delegate without onboarding new users into Bsure first?

## The views

Impact Dashboard surfaces one tab per scope:

### KPI Dashboard

Tenant-wide KPI dashboard.

Data behind the different tiles are accessible for users that have been granted KPI Drilldown permissions.

### My Team

The same KPIs and assessments as [My Organization](/user-guides/impact-dashboard/my-organization.md), automatically scoped to the signed-in user's Entra direct reports. Visible to users with direct reports.

Every line manager already has a scoped view of their team — with no per-manager configuration. Add a manager in Entra, they have the view tomorrow. See [My Team](/user-guides/impact-dashboard/my-team.md).

### My Organization

The configured-scope view — same KPIs and assessments, scoped to whatever slice of the organisation the user is set up to see in *Settings → Configuration → Organization*.

When you need a non-managerial slice (a department, a region, a cost centre), configure it once and route it to the right person. See [My Organization](/user-guides/impact-dashboard/my-organization.md).

### Application Owner

A detailed view on the applications where the logged-in user is set as application owner.

{% hint style="info" %}
**Why you might not see all three tabs.** The tab strip adapts to who you are:

* **KPI Dashboard** is always visible.
* **My Team** renders only when you have direct reports in Entra. Service accounts and flat users see Personal View and Organization, which is correct behaviour.
* **My Organization** is visible to anyone with a configured scope. To grant one, an admin uses *Settings → Configuration → Organization*.
* **Application Owner** is visible if you are set as Owner for any applications. To grant one, an admin uses *Settings → Configuration → Applications*.
  {% endhint %}

## The delegation flow

Every assessment ships with a *Delegate* button. Clicking it opens *Change assessment delegation*:

* **Delegate to** — searches your Entra tenant by name or email. The recipient does not need a Bsure account first; they get the assessment via email and act in whatever tool fits.
* **Open email draft** — drafts a notification message in Outlook (default on).
* **Copy instructions to clipboard** — for any other channel you prefer.
* **OK** to confirm.

The assessment moves from **Active** to **Delegated** on the assigner's view. The receiver sees it as Active on theirs, with a direct link to the finding.

If the receiver later identifies a better owner, they can re-delegate. The chain stays traceable.

{% hint style="info" %}
**Recipients are Entra users, not Bsure users.** Bsure searches the entire Entra tenant, so you can delegate to anyone the organisation employs — engineers, line managers, HR, finance — without onboarding them into Bsure first. They receive the action via email; if they need to act inside Bsure, an admin can grant access via *Settings → Configuration → Users Management*.
{% endhint %}

### Lifecycle: Active → Delegated → Ignored

* **Active** — newly surfaced or untouched.
* **Delegated** — assigned. The original scope owner sees it on the *Delegated* tab; the receiver sees it as Active on theirs.
* **Ignored** — the scope owner has decided this finding isn't relevant for their organisation (a known waiver, an out-of-scope case). Stays on the *Ignored* tab and can be reactivated.

## How it ties back

[KPI Dashboard](/user-guides/impact-dashboard/kpi-dashboard.md) sets the focus. Impact Dashboard distributes it. Receivers act, and the underlying KPI ticks down on the next dashboard cycle. The trend becomes the next leadership review.

## Where to go next

* **Set leadership focus** → [KPI Dashboard](/user-guides/impact-dashboard/kpi-dashboard.md)
* **Hand every line manager a scoped view of their team** → [My Team](/user-guides/impact-dashboard/my-team.md)
* **Configure scopes for non-managerial owners** → [My Organization](/user-guides/impact-dashboard/my-organization.md)
* **For application-scoped findings (renewals, secret expiry, geo-anomalies)** → [Application Owner](/user-guides/impact-dashboard/application-owner.md)

See it. Own it. Fix it. Bsure.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bsure.io/user-guides/impact-dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.