Managing major app updates across many Cloud sites — any org-level view or workflow?

[David Romero]

Hi everyone,

I’m an application administrator for multiple Atlassian Cloud sites. After a vendor told me they’d shipped a new release, I went to review installed apps and noticed a UX/location shift. Previously I’d check per product site under Apps; now (in my tenant) I’m finding I need to go to Administration → Sites and then drill into each site to see installed apps and whether updates are pending.

This makes the process quite tedious at scale because:

1. I don’t see any cross-site overview showing which apps have pending updates unless I open each site one by one.
2. For major releases (where admin consent is required), I’m approving site by site, which doesn’t scale.

Questions for the community (and Atlassian, if you’re here):

• Is there an org-level dashboard, report, or API to list pending app updates across all sites?
• Is Atlassian working on a better admin notification mechanism (inside Admin Center), rather than relying on more vendor emails?
• For Forge apps (Runs on Atlassian), can vendors surface an in-app, admin-only banner with a deep link to the site’s “Manage/Connected apps” page to streamline approvals?
• Any CLI, audit log, GraphQL, or workaround you use to track and plan major-version approvals at scale?
• Tips on rollout playbooks (waves, comms templates, deadlines) that have worked for you?

To be clear, I’m not trying to bypass consent—just looking for a scalable, admin-friendly way to discover and approve majors across many sites.

Thanks!

[Shawn Doyle - ReleaseTEAM]

Hi @David Romero 

I also find this change to be annoying.  I'd suggest writing up a support ticket and see if they will address it.