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.
Concurrent license — for product owners
Issue a shared team key with a max active users cap. Seats are enforced on device activations, not live sessions alone. Use this when you want a device-level audit trail and seats that persist until deactivation.
When to choose Concurrent
- Team license — “5 simultaneous users” for a design team.
- Classroom / lab — many machines, fewer concurrent seats.
- Mid-market alternative to Floating — activation-based seats without session-only semantics.
Issue a license (dashboard)
- Licenses → Generate License.
- Step 1 — choose Online (typical) or Offline activation mode.
- Step 2 — select Concurrent and set Max active users (seat cap).
- Steps 3–4 — product, release, issued-to (optional), entitlements, notes → generate.
Operate & support
- Activations tab — authoritative seat counter (
N / max). - Sessions tab — who is online now (support visibility; does not free seats by itself).
- Deactivate a device activation to free a seat for another machine.
- Block device — deny one rogue laptop without revoking the whole team key.
- Revoke license — disable the entire key from Overview.
Global views: /dashboard/activations and /dashboard/sessions.
API automation
- Create:
POST /api/licenseswithtype: ConcurrentandmaxActiveUsersCount. - Activate:
POST /api/activations(SDK, API key). - Deactivate seat:
DELETE /api/activations/currentor block from dashboard.
See Activations platform guide and REST API.
Concurrent license — for end users
You receive a shared license key (and usually license.bin) from your organization.
Each computer that runs the app consumes one activation seat until the app deactivates or IT removes the device.
What you need
- License key and signed license file from your admin.
- Product public key and API endpoint configured in the app (integrator responsibility).
- Network access if the license uses online validation.
First run
- Install the app and import the license file or enter the key.
- Validate / activate — the server registers this device as one seat.
- While the app runs online, a session heartbeat may show you as “online” in admin tools.
- On exit, use the app’s deactivate action if available so the seat frees for a colleague.
Limits
When all seats are in use, the next device gets Max activations reached. Closing the app without deactivating may keep the seat occupied until an admin clears it.
Troubleshooting
| Message | What it means | What to do |
|---|---|---|
| MaxActivationsReached | Seat pool full | Ask a teammate to deactivate, or contact IT |
| DeviceBlocked | Admin blocked this machine | Contact support |
| LicenseInvalid / revoked | Key disabled | Request a new key from vendor |
| LicenseExpired | Term ended | Renew or request updated license |
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.