Scylla Team licensing is account-based.
A Team organization purchases a quantity of seats, then assigns those seats to organization members. The member signs into Scylla desktop with their Scylla Account to activate the Team entitlement.
No shared Team license key is required for normal Team seat assignment.
The model
Purchased seats
→ Assigned to members
→ Member signs into desktop
→ Scylla receives/verifies Team entitlement
→ Installation becomes Team-active
Membership alone does not guarantee a seat.
An installation alone does not create a seat.
Assign a seat
If your organization role allows seat management:
- Sign in to the Scylla Workbench Team console.
- Open the Team license or seat-management area.
- Locate the organization member.
- Assign an available Team seat.
- Confirm the member now shows as seat-assigned.
The exact controls may be presented under Members, Licenses, or the current Team navigation in your deployed Workbench version.
Seat count
The Team console can show values such as:
assigned / purchased
For example:
3 assigned / 5 purchased
That means two purchased seats are still available for assignment.
Do not confuse purchased quantity with member count.
Removing a seat
Removing a seat releases the organization's assignment from that member.
It does not delete the member from the organization.
It also does not delete the member's local files.
Because it changes entitlement, expect the affected member's Team status to change after account/entitlement refresh.
Seats and installations
Scylla can track desktop installations separately from seats.
A seat is assigned to an account/member.
An installation represents a desktop activation/session associated with that account entitlement.
Do not treat every installation as a separately purchased seat unless the actual Team entitlement rules shown in your console say so.
Revoke an installation
If an installation should no longer remain active, use the Team console's installation controls where your role allows it.
Revoking an installation is different from removing the member's seat.
Use installation revocation when the account remains valid but a particular machine/session should no longer be trusted.
New member workflow
For a new Team member:
- Send the organization invitation.
- Have the person accept it.
- Assign an available seat.
- Have the person install Scylla.
- In Scylla desktop, choose Sign in with Scylla.
- Complete browser sign-in.
- Let the desktop refresh and verify the Team entitlement.
Checkout is not entitlement
A successful browser return from a billing/checkout flow is not itself proof that a Team seat exists.
Scylla uses authoritative account/billing state after the server has processed the payment/subscription change.
If the Team console still shows the old purchased quantity, do not manually fabricate a local seat state. Wait for or refresh the authoritative billing state.
No seats available
If all purchased seats are assigned:
- remove an assignment that is no longer needed; or
- increase the organization's purchased quantity through Billing if your role allows it.
See Billing.
Common problems
Member is in the organization but desktop is not Team-active
Check whether a seat is actually assigned.
Seat is assigned but desktop still shows old status
Sign out/in or refresh the Scylla Account state from the desktop. Confirm the same account is being used.
Purchased quantity changed but seats are still unavailable
Billing state may still be processing. Confirm the Team console shows the new authoritative quantity.
Removing a seat did not remove the member
That is expected. Seat assignment and organization membership are separate.