Deactivated users cannot reactivate their account without admin approval if the instance has reached or exceeded their license count
Problem to solve
We recently implemented the ability for self-managed customers to deactivate users. If those users are able to reactivate their account at any time, admins may not have enough control over the seat management and potential charges that a reactivation of a user may incur.
Proposal
If a user who is deactivated tries to reactivate their account after the instance has reached or exceeded their purchased seat count, they will have to request permission from their sys admin first so the admin can properly manage seats. Admins should be able to toggle this on and off, similarly to #35680 (closed).