Concurrent license
A concurrent license lets a fixed number of devices use the product at once across a team. Seats are enforced through device activations—when a user closes the app, the activation can be released and the seat becomes available for another machine. Unlike Floating, concurrent is not limited to live session heartbeats for seat counting.
Activation seats
Max active users = device activation cap.
Activations tab
Seat usage shown per device row.
Sessions tab
Live connections for support visibility.
Business model
Concurrent is the familiar “N simultaneous users” license sold to teams and SMBs—simpler than enterprise floating servers but same commercial idea: shared key, capped simultaneous use.
- Team license — “5 concurrent users” for a small design team.
- Classroom / lab — 30 machines, 15 concurrent seats; students rotate.
- Branch office — one key per office with concurrent cap vs named users.
- Mid-market alternative to Floating — activation-based enforcement without session-only semantics.
Benefits
- For vendors — clear seat metric on Activations tab; block rogue devices individually.
- For customers — share one license key; seats free when colleagues close the app (per deactivation policy).
- vs Floating — activations persist until released—better when you need device-level audit trail per seat.
Logic of use (how seats work)
When max active users = 5, the server allows up to 5 device activations on the license. Each new machine activates until the cap is reached; further activations fail until a seat frees.
Live sessions still appear on the Sessions tab for online concurrent licenses—they show who is connected right now, but seat enforcement uses activations, not session count alone.
Concurrent can run with online validation (typical) so revocation and compliance apply in real time. It is not the same as Floating’s “always online + session-only seats.”
Example lifecycle
Startup buys Concurrent, max 5. Five engineers activate on five laptops Monday. Sixth engineer fails until one deactivates or IT removes an activation from Activations tab. Engineer closes app and client deactivates → sixth engineer can activate.
IT sees unknown device on Activations list, blocks activation. Stolen machine fails on next online check without revoking entire team key.
Lifecycle stages
- Issue — type Concurrent + max active users.
- Distribute — shared team key.
- Activate — each device consumes one activation seat.
- Operate — monitor Activations tab; Sessions for live view.
- Release seat — client deactivation or operator block/remove.
- Revoke — disable whole license from Overview.
Dashboard workflow
- Create → Concurrent → max active users in step 2.
- License detail → Activations tab (seat enforcement).
- Sessions tab — who is online now.
- Global
/dashboard/activationsfor cross-license support.
Concurrent vs Floating
- Seat counter — Concurrent: activations; Floating: live sessions.
- Online rule — Floating: always online; Concurrent: online validation typical but not “always online type” in policy.
- Dashboard — Concurrent shows Activations tab; Floating hides it and uses Sessions only.
- Best for — Concurrent: team device audit; Floating: large org with rapid seat churn.