For the complete documentation index, see llms.txt. This page is also available as Markdown.

Scoped Views & Delegation

Where leadership focus turns into accountable ownership.

The KPIs from Progress become named, owned, actionable assessments across three scoped views — My Team, My Organization, and Application Owner — 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, 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.

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.

Application Owner

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

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.

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.

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.

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.

This is a different mechanism from Accept risk on Assessments — that flow requires a reason and a review date, and keeps an audit trail. These three scoped views still use the simpler Ignore.

How it ties back

Progress 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

See it. Own it. Fix it. Bsure.

Last updated

Was this helpful?