Confluence currently emits avi:confluence:deleted:user when a user account is deleted, but there is no corresponding event when a user account is simply deactivated.

In Atlassian Cloud, deactivation, not deletion, is the dominant off-boarding path. Org admins deactivate accounts (often automatically via SCIM / IdP sync) and rarely fully delete them, since deletion has implications for content attribution and audit history.

We'd like to request that Confluence also emit a product event for deactivated users such as avi:confluence:deactivated:user that Forge apps can subscribe to via the trigger module.

Without a deactivation event, Forge apps have no real-time signal that a user has been off-boarded. Our only available workarounds are:

1. Polling the user list on a scheduled trigger. It's wasteful, slow, and rate-limit-sensitive at scale.
2. Lazy-checking each user on read, which adds latency to every page load.

A first-class deactivation event would allow Forge apps to reconcile data in near real-time, the same way deleted:user already does for full deletions.