Team licenses

Team licensing is centralized billing plus claim-link distribution. It is not a full seat-management system.

How it works#

1. A billing manager signs in on soloterm.com and buys a team subscription with the number of seats they need.
2. The team dashboard creates a license pool for that subscription.
3. The billing manager generates a claim link and shares it in Slack, email, or wherever the team coordinates.
4. Each teammate opens the link, signs in or registers, and claims a seat.
5. Solo creates a normal Solo Pro license on that teammate's account.

Claim links#

Claim links are first come, first served. Anyone with the link can claim while the license pool is active and seats remain.

The dashboard shows the raw claim URL only once after generation because Solo stores only a hash of the link. Copy or share it when it appears. Regenerating the link replaces the previous one.

What teammates get#

A claimed team license appears in the teammate's account alongside any other licenses. If a team-license flow provides a license key, enter it through Solo's regular license activation. Solo submits the key and this device's details to soloterm.com for validation. If the service accepts it, the desktop stores it in the same licensed state used for other accepted keys; Solo Desktop has no separate Team license type.

Claimed licenses stay active while the team subscription is active. If the subscription is canceled, claimed licenses remain valid through the end of the already-paid period and then expire. Scheduling a cancellation does not block claims — open seats stay claimable until the paid period actually ends.

Auto-growing seats#

Optional, and off by default. Set an auto-grow limit on the team dashboard and a claim against a full pool automatically adds a seat to your subscription instead of failing. Stripe prorates the charge and bills it immediately — if the charge cannot be collected, the claim is declined and nothing is added. The pool never grows past your limit: normally it adds one seat per claim, and if claimed seats ever exceed your billed quantity, the next auto-grown claim bills the difference in one update.

While auto-grow is on, anyone holding your claim link can add billed seats up to that limit — so set it to what you actually expect to need. If you'd rather keep spend fixed, buy your seats up front and leave auto-grow off.

Leave the limit empty to keep a fixed seat count — a full pool then simply stops accepting claims.

Revoking a seat#

The team dashboard lists every member with their name, email, claim date, and status. Revoke a seat from there when someone leaves the team: their license stops validating immediately, they get an email letting them know, and the seat opens up for someone else to claim with the same link.

Revoked someone by mistake? Use Send feedback in Settings > Account to describe the situation. While a seat is open, the member can simply claim again with your claim link, which reactivates their license with the same key. The seat itself stays purchased; reduce your seat count in the billing portal if you don't plan to replace them.

Refunds#

A full refund of the original purchase or a renewal ends the team immediately: every claimed license expires right away and the subscription is canceled so you are not billed again. Partial refunds and refunds of prorated seat-change charges are billing corrections only — they never affect member licenses.

What team licensing does not include#

Team licensing does not include domain gating, SSO, assigned-seat UI, or directory sync.

To change how many seats can be claimed, the billing manager changes the subscription quantity in Stripe billing.