Issue Summary

Enterprise admin is unable to reactivate a workspace member who was previously deactivated under a deprovisioned enterprise. Clicking "Reactivate" returns the error "Must reactivate user first" (HTTP 403). The member's Atlassian account is active and holds an active license in the current enterprise, but the workspace retains stale enterprise-level deactivation status from the old (deprovisioned) enterprise.

Steps to Reproduce

1. Member is deactivated at the enterprise level under Enterprise A

1. Enterprise A is deprovisioned

1. The workspace is migrated to a new Enterprise B

1. Member's Atlassian account is active and holds an active license in Enterprise B

1. Enterprise admin navigates to Workspace → Members → Deactivated

1. Admin clicks "Reactivate" on the affected member

Expected Results

Member is successfully reactivated in the workspace under the current active enterprise (Enterprise B), and regains access to the workspace and its boards.

Actual Results

Reactivation fails with the error: "Reactivate the Member first."

Workaround

Remove the affected member from the workspace and re-add them. The member will regain access to the workspace and the current enterprise.

Note: This workaround resets the member's board memberships within the workspace — they will need to be manually re-added to relevant boards.