Hey everyone, running into a frustrating snag with 1Password Business admin reports. Our company has grown to just over 600 users, and now any time I try to run a report (like inactive users or vault access), the whole admin console just freezes. Spinning wheel forever.
It works fine if I filter down to a specific team of under 100 people. Has anyone else hit this wall with a larger user base? Is there a trick to this, or is it a known limitation? Really hoping there's a fix—reports are key for our security audits. Thanks!
dk
That's a classic symptom of a report generation process moving from in-memory operations to needing proper pagination or streaming when the dataset crosses a certain threshold. The fact it works for sub-100 groups confirms it's not a permission or API failure, but a performance cliff.
From an architectural perspective, the admin console is likely trying to fetch, aggregate, and render all 600+ user objects synchronously before painting the UI. This creates a blocking chain: network I/O, database query time, and client-side processing all compound. A team filter probably triggers a more efficient, indexed database query and returns a smaller payload that the browser's main thread can handle without locking up.
You've likely hit a client-side rendering bottleneck, not a server-side one. A proper fix would require the frontend to implement virtualized rendering or the backend to offer a true asynchronous report generation endpoint you could poll. For a temporary workaround, see if your browser's developer tools show a long-running script warning on the Network or Performance tab when you attempt the full report. That would pinpoint whether it's the data fetch or the data processing that's causing the freeze.
Latency is the enemy
Yep, hit that exact wall at about 550 users. The UI just gives up. The trick I found is to never use the "Run Report" button directly from the main Reports page for a full org report. It tries to do everything at once and chokes.
Instead, go to the specific area for the data you want. For inactive users, go to Directory > People, use the "Last Active" column filter, and then export *that* filtered list. It uses a different, paginated backend query. It's a workaround, but it gets you the CSV for your audit.
You're right, it feels like a hardcoded client-side limit. Have you opened a ticket with support? The more of us who report it, the sooner they might prioritize a proper async fix for the reporting dashboard.
pipeline all the things