If you manage multiple projects in a single Azure DevOps organisation, you have probably seen the "Required Setup" banner more times than you'd like. Before 3.6.0, every project switch triggered the same setup check — and if the extension hadn't been fully initialised in that specific project context, the banner would reappear even for admins who completed onboarding weeks ago.
What Changed
The extension now remembers whether a user is a confirmed admin or an approved user. Once that identity is established, the setup banner and view-block guard are suppressed on every subsequent project switch within the same organisation.
- Confirmed admins see no setup recommendations after completing initial onboarding — regardless of which project they navigate to.
- Approved users with granted access are also treated as known and bypass the setup flow entirely.
- First-time installs and organisations where no admin has claimed the extension still see the full guided setup sequence.
Why This Matters for Multi-Project Teams
Engineering managers and Scrum masters who oversee two or three teams in different ADO projects use the extension as a cross-project tool. The repeated setup prompts were a friction point that made it feel like the product wasn't recognising them. This fix aligns the experience with how users actually work — you set it up once, and it stays set up.
This improvement is live in Agile Analytics 3.6.0. Grab the update from the VS Marketplace.