## TL;DR
The user already holds a license or add-on that conflicts with the new assignment. Open their Zoom admin profile, note the current license type and add-ons, remove or change the conflicting one, then assign.

```text
"Zoom license assignment failed" user already has add-on
```

## Use this when
- Zoom license assignment fails citing an existing license or add-on.
- The user was recently moved between teams or plans.
- An add-on assignment fails specifically.

## Not for this skill when
- The org is out of licenses. That is a purchasing problem.
- SSO provisioning assigns the wrong type. Fix the mapping, not the user.
- The user cannot be found. That is a directory sync problem.

## Steps
1. Open the user's profile in the Zoom admin portal. Verify: you see the current license type and add-ons.
2. Identify which existing item conflicts with the new assignment. Verify: you can name it.
3. Remove the conflicting add-on or change the base license type. Verify: the conflict is gone.
4. Retry the assignment. Verify: it succeeds.
5. Confirm the user's effective license. Verify: it matches what was intended.

## Variant phrasings
### Zoom license conflict
The short phrasing.
### add-on already assigned
The item-first search.
### Zoom user license error
The generic phrasing.

Compatibility: Zoom admin license management, all account types with licensed users.

## Why it happens
Zoom allows one base license per user, and add-ons attach to specific base types. Assigning a second base or an incompatible add-on is rejected rather than merged.

## Edge cases / pitfalls
- Pending invitations holding a license reservation on the user's email.
- SSO-provisioned license types overriding manual assignment on next login.
- The add-on requiring a base the user does not have.
- Webinar or phone add-ons with their own separate assignment rules.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Wu2HXE-pis-2dI12tyBrYA