SASVA License/Seat Not Released After User Offboarding, Blocking New Assignments
Problem
A newly onboarded employee is unable to log in to SASVA, or logs in but sees a "No license assigned" / "Access restricted" style message, shortly after another employee left the organization or was offboarded. Alternatively, a returning/rehired employee is blocked from getting a new SASVA seat even though a seat should be available.
Symptoms
- New hire's SASVA login succeeds (SSO/auth works) but chat features are disabled or a licensing/entitlement error is shown.
- The organization's total active SASVA seat count appears full even though a recently offboarded user should have freed up a seat.
- A departed employee's account still shows as an active seat in the admin/license view days or weeks after their last day.
Root Cause
SASVA seat/license assignment is tied to the user's account record, not automatically reconciled with HR offboarding events. When an employee leaves, their SASVA seat is not released automatically — it must be explicitly deprovisioned by an administrator. Until that happens, the seat remains "occupied," which can block new seat assignments if the organization is at its licensed seat limit.
A secondary contributor is directory sync delay: if SASVA user provisioning is driven by an AD/SSO group sync, a departed user removed from AD may still appear in SASVA's user list until the next sync cycle runs, further delaying seat release.
Resolution/Workaround
For a new hire blocked by a full seat count
- Confirm with your SASVA administrator whether the organization is at its licensed seat limit.
- Identify offboarded users still holding an active seat via the SASVA admin/license management view.
- Have the administrator explicitly deactivate/deprovision the departed user's SASVA account to release the seat.
- Assign the freed seat to the new hire and have them retry login.
Preventive process (recommended for admins)
- Add SASVA seat deprovisioning as an explicit step in your organization's standard offboarding checklist, alongside other SaaS/tool deprovisioning steps.
- Periodically audit the SASVA license/seat report against your active employee/HR roster to catch orphaned seats.
- If SASVA provisioning is driven by an AD/SSO group, confirm the sync frequency and align offboarding timing accordingly, or trigger a manual sync after offboarding a user.
Escalation
If seat counts do not reconcile after manual deprovisioning, or if the license management view does not reflect a deactivated user, contact sasva_support_in@persistent.com with the affected user's email, organization name, and the current seat count shown in the admin view.
Comments