Skip to main content
GullySystem
A practical guide

Why one licence key ends up shared by a whole team

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 5 min read

In this guide 6 sections
The short answer

A buyer orders five seats, receives one key, and forwards it to whoever needs the software, so activation counts climb far past the seat count. Close the gap with per seat keys, named users or a customer portal that lists the seats in use and lets the administrator remove a leaver.

How five seats become twenty users

The order says five seats. The fulfilment email carries one key, and the buyer is a team lead, not an administrator, so the easy move is pasting it into a chat channel.

A month later two contractors join and a designer replaces a laptop, and each needs the software while the key sits in the channel for anyone to copy. Nobody decides to break the licence. It happens one helpful message at a time.

Weigh this before calling it theft. Most sharing is a delivery problem, because the buyer was given no sensible way to hand out five separate seats to five people on the team.

What seat and activation counts reveal

Compare two numbers for each key. Seats are what the order paid for, activations are the machines that registered the key, and a wide gap means one key is doing the work of many.

Read the pattern, not just the total. Twenty activations from one office in a single week suggest a rollout, and a slow climb with changing machine names and different laptops suggests staff turnover. Several cities mean a leaked key.

You need an activation log for this. If your shop does not store the date, the machine name and the network address of each activation, the first fix is to start recording them.

  • Seats paid for against activations used
  • Date of each activation
  • Machine name on each activation
  • Network address or region
  • Activations that were released and reused

Why buyers do it and what it costs you

Some buyers are careless. Most are busy, having bought on a manager’s card with no admin screen and a hard to find licensing page, so sharing becomes the path of least effort. In a small studio the shared key is a favour, but in a larger firm it is a procurement gap, because nobody in purchasing knows the licence exists.

The cost shows up in three places. Revenue is lost when later seat purchases never happen, support is pulled in when a key hits its activation limit, and your records cannot show who uses the product. Every renewal conversation then becomes a guess.

A softer cost follows. When you finally tighten the rules, you tighten them on customers who never knew there was a rule, and the first they hear of it is a refusal.

Options from per seat keys to a seat portal

Simplest fix: one key per seat. An order for five seats sends five keys, each tied to a single activation, which explains itself and lets the buyer hand them out one by one.

Named users go further. The buyer signs in to a portal and adds colleagues by email address, and each person receives a personal key or sign-in. When someone leaves, the manager removes them and the seat returns to the pool for the next hire to use straight away.

A seat portal is the most useful option, since it shows seats in use, seats free and who holds each one, and extra seats are one click away.

  • One key per seat sent at delivery
  • Named users added by email address
  • Portal showing seats in use and seats free
  • Remove a user and return the seat
  • Button to request more seats

Start by reading your own order data

Pull the last year of seat orders. Match each one to its activation log and mark the keys where activations exceed seats, which gives you a real list instead of a suspicion. Start at the largest gap.

Write to those customers in a friendly tone, stating the seat count, the activation count and the simple way to add seats. Most will answer with an order. Some will thank you.

Then change delivery for new orders, so the problem stops growing while you work through the backlog of old keys one customer at a time.

Seat and activation audit sheet

Each key sits on one line of the sheet, with columns for customer, product, seats paid for, activations used, latest activation date and regions seen. The last column names the next step. The choices are to leave the key alone, write to the customer, or move the order to per seat keys with a short note.

Open a blank worksheet to print

Questions owners ask

Is a shared key always a breach of licence?

Check the licence terms. Some allow a team to install on several machines under one key, others tie each seat to a person, and the terms printed at purchase decide it.

How can I tell sharing from a real rollout?

Look at timing and place. Many activations in a few days from one office is a rollout, while slow growth across different regions and machine names suggests the key has left the company.

Will per seat keys annoy genuine buyers?

Rarely, if the delivery is clear. Five keys in one email, each labelled, are easier for an administrator to hand out than one key with an unwritten limit that nobody can enforce.

What if our publisher issues only one key per order?

You can still wrap it. A portal can record who in the customer’s team uses the key and show the seat count against activations, even when the key itself is a single string.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Share Your Requirements