> For the complete documentation index, see [llms.txt](https://docs.bsure.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsure.io/user-guides/scoped-views-and-delegation.md).

# Scoped Views & Delegation

Where leadership focus turns into accountable ownership.

The KPIs from [Progress](/user-guides/progress.md) become named, owned, actionable assessments across three scoped views — [My Team](/user-guides/scoped-views-and-delegation/my-team.md), [My Organization](/user-guides/scoped-views-and-delegation/my-organization.md), and [Application Owner](/user-guides/scoped-views-and-delegation/application-owner.md) — all sharing the same delegation flow.

Instead of *"we have N inactive users"* sitting on IT's plate, the picture becomes *"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 three scoped views

### My Team

The same KPIs and assessments as [My Organization](/user-guides/scoped-views-and-delegation/my-organization.md), automatically scoped to the signed-in user's Entra direct reports. Visible to users with direct reports, with no per-manager configuration. See [My Team](/user-guides/scoped-views-and-delegation/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*. Use this for a non-managerial slice: a department, a region, a cost centre. See [My Organization](/user-guides/scoped-views-and-delegation/my-organization.md).

### Application Owner

A detailed view on the applications where the logged-in user is set as application owner. See [Application Owner](/user-guides/scoped-views-and-delegation/application-owner.md).

{% hint style="info" %}
**Why you might not see all three.** Each view is visible only to the people it applies to:

* **My Team** renders only when you have direct reports in Entra.
* **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 on these three views 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.

{% hint style="info" %}
This is a different mechanism from **Accept risk** on [Assessments](/user-guides/assessments.md) — that flow requires a reason and a review date, and keeps an audit trail. These three scoped views still use the simpler Ignore.
{% endhint %}

## How it ties back

[Progress](/user-guides/progress.md) sets the focus. These scoped views distribute it. Receivers act, and the underlying KPI ticks down on the next cycle. The trend becomes the next leadership review.

## Where to go next

* **Set leadership focus** → [Progress](/user-guides/progress.md)
* **See your own prioritized worklist** → [Dashboard](/user-guides/dashboard.md) and [Assessments](/user-guides/assessments.md)
* **Hand every line manager a scoped view of their team** → [My Team](/user-guides/scoped-views-and-delegation/my-team.md)
* **Configure scopes for non-managerial owners** → [My Organization](/user-guides/scoped-views-and-delegation/my-organization.md)
* **For application-scoped findings (renewals, secret expiry, geo-anomalies)** → [Application Owner](/user-guides/scoped-views-and-delegation/application-owner.md)

See it. Own it. Fix it. Bsure.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bsure.io/user-guides/scoped-views-and-delegation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.