Skip to content
License Server v1.39.0 · released 17 Nov 2026release notes →
Skip to content

Seat Activity and the Shared-Key Flag ​

License Server 1.36.0 or later, and Console 1.22.0 or later. Hosted accounts have both.

License Server keeps a short history of each license's seats, and from it flags licenses that look shared: licenses whose key seems to be passed between more people than it has seats for. The flag is there so you can notice and follow up. It never blocks, revokes or changes anything by itself.

What is recorded ​

For each license, the server records a seat event whenever:

  • a machine takes a seat (a new machine activates);
  • a machine is turned away because the license is full;
  • a seat is freed, together with who freed it:
    • the buyer's app, deactivating with its own token;
    • the buyer portal, when the buyer frees a machine there;
    • you, from the console or POST /v1/admin/deactivate-by-instance-id;
    • Casazium support, on a hosted account;
    • lease expiry, when a machine's seat lease ran out and a new machine took the seat.

Each event holds only its type, time, who freed it, and a machine code: a short value worked out from the license key and the machine's instance_id. It tells machines apart on one license, but it isn't the instance_id, and the same machine has a different code on every license. No IP address or location is recorded.

Events are kept for 90 days and then deleted automatically. A machine that re-activates on the same instance_id (a reinstall, for example) doesn't add a new seat; it isn't counted twice.

When a license is flagged ​

A license is flagged when either of these is true.

More machines than seats ​

The server counts how many different machines used the license in the last 30 days. A machine counts if it:

  • holds a seat right now; or
  • took a seat in the last 30 days; or
  • was freed in the last 30 days by the buyer's app, the buyer portal, or lease expiry.

Machines that you or Casazium support freed don't count, on the reasoning that those are support actions, not the buyer's own use. Each machine counts once, however often it came and went.

From that number it subtracts the license's seats, using the largest of its seat limit, the seats it holds now, and the seats it held at the start of the 30 days. Using the largest means a downgraded license, whose buyer is still on (or just removing) the machines from before, isn't treated as sharing. What's left is the number of extra machines.

The license is flagged when the extra machines reach the threshold:

  • 3, for licenses up to 15 seats;
  • 20% of the seats, rounded up, for larger licenses: 4 extra for 16 seats, 10 extra for 50 seats;
  • or whatever the product's setting says (see The setting).

Licenses with unlimited activations are never flagged.

Several machines turned away ​

If 5 or more different machines are turned away in the last 24 hours because the license is full, it's flagged too. One machine retrying over and over counts once. This can also catch someone filling a license's seats with made-up machines, which locks the real buyer out. To free those seats, use the license's Activations table in the console, or deactivate by instance ID with the instance IDs it lists (the machine codes in the seat history aren't instance IDs).

Examples ​

For a license with 3 seats, over the last 30 days:

What happenedMachines that used itExtraFlagged?
The buyer uses their 3 computers, nothing changes30No
The buyer reinstalls on the same computer30No
The buyer replaces one laptop41No
The buyer replaces two machines52No
6 people take turns with the 3 seats63Yes
6 people share by letting leases expire instead of deactivating (licenses with a lease)63Yes
The license is cut from 10 seats to 3, and the buyer frees 7 machines100No
You free 3 stale seats for the buyer, who sets up 3 new machines30No
A team rotates the seats every 45 days6 for about 30 of every 45 days3Yes, for part of the time

A 1-seat license whose buyer rebuilds the same computer 3 times in a month, getting a new instance_id each time and freeing the old one in the buyer portal, shows 4 machines and 3 extra, so it is flagged. See False alarms.

Seeing it in the console ​

  • Licenses list: a flagged license shows a Looks shared badge under its seat count.
  • The license's page: a Seat activity section under Activations. When the license is flagged, it says why in plain words; for example "7 machines used this license in the last 30 days, 4 more than it had seats for." Below that is the history: the newest 200 events in the last 90 days, each with its time, what happened, the machine code, and holds a seat for machines that have one now.
  • The data export includes every license's seat events (see Exporting your data).

The setting ​

Each product has a Shared-key flag setting, under Products → Edit:

ChoiceWhat it doesUse it for
Automatic (default)3 extra machines, or 20% of the seats for licenses over 15 seatsMost desktop apps and developer tools
OffNever flags this product's licenses, by either ruleApps that run on CI servers or throwaway VMs, which get a new identity each run
CustomFlags at exactly the number of extra machines you choose, 1 to 1000, whatever the license size. 5 machines turned away in a day still flag a licenseBeing stricter or more lenient than Automatic

A few things to know:

  • A low custom number flags ordinary changes. With 1, a single laptop replacement flags the license.
  • Off silences both rules, including the warning for someone filling the seats with made-up machines. The history is still recorded and listed on the license's page, refusals included, and the API still returns the counts, so you can look at any time.
  • The setting takes effect immediately, on every license of the product, including ones already flagged.
  • A license with no product (issued before products existed, or whose product was deleted) uses Automatic.

Through the API, the setting is sharing_flag on PATCH /v1/admin/products/{id}: "auto", "off", or a whole number from 1 to 1000.

What to do when a license is flagged ​

A flag is a reason to look, not proof. Start with the history on the license's page:

  • Many machines coming and going, close together: the key is probably being passed around, or a team is sharing one license.
  • A few new machines spread over weeks: more likely hardware replacements, or rebuilds.
  • Many refusals from machines that never held a seat: someone may be trying keys, or filling the seats on purpose.

Then decide. In most cases the best first step is a friendly email to the buyer, offering the right number of seats rather than accusing anyone:

Hi — we noticed your license for Acme Pro has been used on more computers this month than it has seats for. If your team needs more seats, we can add them: just reply and we'll set it up. If something else is going on (a lab, test machines, rebuilds), let us know and we'll make sure your license fits how you use it.

After that you can:

  • Add seats, or offer a team license, by changing the license's terms;
  • free stale machines for the buyer on the license's page;
  • turn the flag off for products used on CI or VMs;
  • revoke the license, as a last resort, when it's clearly being resold or published.

Nothing happens to the license or the buyer unless you do one of these.

False alarms ​

The flag counts machines, and some honest setups create many:

  • CI servers, build agents and throwaway VMs that get a new instance_id on every run. Use Off for such a product.
  • Repeated rebuilds on a 1- or 2-seat license, when the app's instance_id changes with each rebuild. A higher Custom number helps.
  • A company replacing many machines at once. The flag clears by itself once the old machines are more than 30 days in the past.

Privacy ​

  • Hosted: Casazium processes seat events on your behalf, as described in the Privacy Policy and Annex I of the Data Processing Agreement.
  • Self-hosted: seat events stay in your own database.
  • Exports and deletion: the data export includes them (the newest 1,000 per license). Deleting a license, or your account, deletes its events at once.

API ​