📊 Improving capturing of deleted users in Data API users table

What's changing

We've made an internal update that improves how Moveworks calculates user roster metrics in analytics, so they more accurately reflect your current roster.

Why

Previously, when a user was removed from your roster in Setup, that removal wasn't always reflected in analytics — so they could still be counted as "active in roster." This update corrects that, so your metrics now stay in sync with what's actually configured in Setup.

Please note this was only in the case of the deleted users. Once user is removed from the roster they are still part of the API response for 7 days before being completely removed from the API

What you'll notice

• "Users active in roster" metrics — You may see a one-time decrease at cutover. This is expected and intended: it reflects previously-removed users no longer being counted, not a loss of data. Your metrics will be more accurate going forward.
• "Users with access to bot" metrics — Essentially unchanged (typically within a few percent). If your dashboards and reports key off bot-access metrics, you should see little to no difference.

Do I need to do anything?

No action is required. If you build your own reporting on roster/active-user counts, just be aware of the one-time step-change at cutover so it isn't mistaken for an anomaly. Metrics based on bot access are effectively unaffected.