Show & tell: one global Current / All-orgs scope toggle next to the org picker

[bdunncompany]

For a partner/MSP login, "am I looking at one org or all of them?" was inconsistent across Breeze, and that bugged me enough to fix it.

Devices and Alerts each had their own per-page Current / All-orgs toggle. Most other list pages (Incidents, Scripts, Patches, Remote Access, Reports, Audit, Logs, Security, and so on) had no toggle at all and just leaned on whatever was in the org picker. On a handful of them the server ignored the org entirely and returned partner-wide data, with nothing on screen telling you that's what you were seeing.

So the same picker value meant different things depending on the page. Sometimes "Acme Co" meant only Acme. Sometimes it meant everything. You had to learn the rule fresh on every screen.

We pulled the toggle out of the individual pages and made it one global control that lives next to the org picker in the header:

How it works:

• A single Current / All orgs pill, left of the org picker. Hidden when your login only has one org.
• Flipping it sets one scope value in the store. Every authenticated request reads it: Current injects your selected org, All orgs spans every org your login can see. Individual pages don't each reimplement the logic.
• It's persisted, so it survives a reload.
• Picking a specific org from the dropdown while you're in All-orgs mode flips you back to Current automatically, so you don't get stuck.

Net result is one mental model everywhere. The pill is the single source of truth for scope, and it's visible from every screen.

The toggle itself is the surgical part: an OrgScopePill component plus a one-line change to the org provider that requests already run through. PR is #972.

Two things worth a maintainer's take:

1. Some endpoints (most of /security/*, and /patches) historically ignored the orgId param and always returned partner-wide data. There's a companion change that narrows those server-side so "Current org" actually narrows them; without it the pill looks like it does nothing on those pages.
2. Default scope is Current. Is that the right default, or should a partner login open in All-orgs on first load? Easy to flip either way.

Happy to cut this however is easiest to review.

[bdunncompany]

Focused PR is #985 (toggle-only, 5 files off current main). The earlier #972 turned into a large web-enhancement bundle and is being superseded by #985.

[ToddHebebrand]

Shipped — the global Current / All-orgs scope pill landed on main in #985 (toggle-only, 5 files), with the follow-up #990 making the pill refresh all list pages on flip. The oversized #972 was correctly superseded.

On the two maintainer questions you raised:

Default scope = Current is the right call — keeping it. A partner login opening straight into all-orgs is a lot of data on first paint and the wrong default for MSP demos; all-orgs should be a deliberate flip.

Server-side narrowing of /security/* + /patches — this is already done. Those read endpoints honor orgId: the compliance/patches gap you flagged closed the same day in #973 (with a 192-line org-scope-narrowing.integration.test.ts), and the security read endpoints (status, threats, posture, recommendations, all five compliance cards, dashboard) all accept and apply orgId. The two security endpoints without an orgId param (/scans, /policies) are non-org-scoped by design — per-device scan history and partner/system policy templates, not fleet list pages the pill drives.

Net: one mental model everywhere, server-side narrowing in place. Thanks for the writeup. Closing as shipped.