License Compliance

On this page

A software license's compliance status tells you whether its allocations satisfy the license's quantity, policy, and restriction rules. Alloy Navigator calculates the status and the license's usage counters in one place and stores the result for each license. Every place that shows license compliance, the Web App included, reads that same stored result, so the figures are identical wherever you see them.

Usage counters

The entitlement of a license is its license quantity and nothing else: a site license, for example, is not expanded into a number of seats. Usage is counted as follows. When the license is retired, or its policy's tracking type is None (the policy does not track usage), every usage count is zero; a retired license also has its quantity set to zero.

Counter What it counts
Quantity The license quantity, or 0 if the license is retired.
Allocated Under a policy that tracks usage by user: the allocations to people who are not Inactive. Under a policy that tracks usage by device owner: the number of distinct owners of the allocated computers and hardware items, skipping retired ones. Under any other policy: the allocations to computers or hardware items that are not retired.
Reconciled 0 under a by-user policy. Otherwise, the number of matches between an allocation to a non-retired computer or hardware item and a detected installation, on that device, of a product mapped to the license's tracked software. One allocation counts once for each matching installation.
Unreconciled Allocations 0 under a by-user policy. Otherwise, Allocated minus Reconciled, never less than 0.
Upgraded The sum of Allocated over every license that upgrades this one and belongs to the same tracked software.
Used Allocated plus Upgraded.
Available Quantity minus Used, never less than 0.
Required Used minus Quantity, never less than 0.

A license can name the license it upgrades. This is the only upgrade concept: there are no downgrade rights, and nothing grants an entitlement to run an earlier version. The upgrade link affects the figures only between licenses of the same tracked software. A license cannot upgrade itself or one of its upgrades; such a change is rejected with "The license cannot upgrade itself or one of its upgrades."

Compliance checks

Alloy Navigator runs the checks below in this order, and the first check that applies decides the result. Checks 8-10 never apply to a license under a by-user policy.

Order Condition Result
1 The policy is No License Required. Compliant.
2 The policy is Site License, and the license has neither an Organization nor a Location restriction. Not compliant: the compliance terms cannot be verified because there are no site rules.
3 The policy is Named Computer, and the license has no Device Name restriction. Not compliant: allocated to a non-matching computer.
4 The license has no policy. Not compliant: no policy.
5 The policy's tracking type is not None, and Required is greater than 0. Not compliant: license count exceeded.
6 Under a by-user policy: an allocated person does not match the Location, Organization, or User restriction. Not compliant: non-matching location, organization, or user.
7 Under any other policy: an allocated computer or hardware item does not match the Location, Organization, Device Name, or Device Owner restriction. A device with no owner is not checked against the owner restriction. Not compliant: non-matching location, organization, computer, or owner.
8 The license has an installations-per-user rule, and a device owner has more reconciled allocations than it allows. Not compliant: too many installations per user.
9 A CPU rule applies, and an allocated computer has more CPUs than the licenses on it allow. Not compliant: more CPUs than the license allows.
10 A CPU core rule applies, and an allocated computer has more cores than allowed. Not compliant: more CPU cores than the license allows.
- None of the above. Compliant.

How checks 6 and 7 treat restrictions:

  • A restriction is checked only when the license has it. A license with no Location restriction is never out of compliance for location.
  • An allocated item passes when one combination of the license's restriction rows passes every kind of restriction the license has. Matching any one Device Name, User, or Device Owner row satisfies that kind.
  • The Location and Organization checks compare the allocated item with the organization and location of the license record itself. A Location or Organization restriction row only decides whether sub-locations or sub-organizations also match.
  • The license is out of compliance as soon as one allocated item fails. An allocation that conforms does not make up for one that does not.
  • When allocations fail for different reasons, the reason reported is not necessarily the one earliest in the order above.

For checks 9 and 10, Alloy Navigator gathers every license that has a CPU or core rule and either belongs to the same tracked software or is allocated to one of the same computers. It adds up the CPUs and cores those licenses allow on each computer, per tracked software, and compares the total with the computer's CPU count and core count. Recalculating one license therefore also sets or clears the CPU or core violation of the other licenses on that computer.

NOTE: Expiration is not part of the stored result. A license whose expiration date is in the past shows as not compliant even when its stored result says compliant; in that case the reason given is that the license expired. A license with the No License Required policy always shows as compliant.

Tracked software compliance

A tracked software record's figures are a separate calculation from the per-license one. They add up the stored results of the record's licenses, and the record can be not compliant for reasons no single license fails for.

The record is not compliant when at least one of its licenses is not compliant, counting expiration as above. In addition, when the record's licenses use at most one tracking type other than None, and none of them tracks usage by user, the record is also not compliant in either of these cases:

  • It has no licenses, but installations of its software have been discovered.
  • An installation of its software is on a device that has no allocation at all, and none of the record's licenses has a policy whose tracking type is None.

In that case, retired licenses are skipped when the licenses are checked. When the licenses use more than one tracking type other than None, or any of them tracks usage by user, the record's status comes only from the status of its licenses, however many unallocated installations there are.

The record's counters:

  • Discovered counts the non-retired installations of all products mapped to the tracked software. Unreconciled installations are Discovered minus Reconciled, where reconciliation applies.
  • Quantity, Used, and Available leave out a license that upgrades another license of the same tracked software, because its allocations already count in the upgraded license's Upgraded counter.
  • Required is the sum of the licenses' Required counters. When reconciliation applies and Discovered is greater than Reconciled, Discovered minus Reconciled is added to that sum.
  • When any license of the record has a policy whose tracking type is None, the Allocated, Upgraded, Used, Available, Required, unreconciled-installation, and unallocated-installation counts are all zero. Only Discovered, the total license quantity, and the number of licenses keep their values.
  • Reconciled is zero when any license of the record has a policy whose tracking type is None or By User.

When the figure is recalculated

A license's stored result is recalculated for that license when one of these events occurs:

  • A software license is created. Its upgrade target, if set, is recalculated too.
  • A license's expiration date, quantity, status, organization, location, policy, tracked software, installations-per-user rule, CPU rule, or core rule changes. When the license it upgrades changes, the new upgrade target is recalculated; the old one is recalculated only when the link is cleared.
  • An allocation is added or deleted. The license and its upgrade target, if set, are recalculated.
  • An Organization, Location, Device Name, or person restriction row is added, changed, or deleted.
  • A product is mapped to or unmapped from a tracked software. Every license of that tracked software is recalculated.
  • An installation is added or deleted. Every license allocated to that device is recalculated.
  • A computer's name, organization, location, status, CPU count, or core count changes. Every license allocated to that computer is recalculated.
  • A hardware item's name, organization, location, or status changes. Every license allocated to that item is recalculated.
  • A person's status changes. Every license allocated to that person is recalculated.
  • The database schema is deployed or redeployed. Every license is recalculated.

NOTE: No recalculation runs when a device's owner changes, or when a person's organization or location changes. The owner-based counters and checks, and the by-user location and organization checks, keep their previous values until another event recalculates the license.

In 2026.1, the upgrade link counts only between licenses of the same tracked software, both in a license's Upgraded counter and in the tracked software figures that leave out an upgrading license. In earlier versions, a license counted toward the Upgraded counter of the license it upgrades even when the two belonged to different tracked software, so the Upgraded, Used, Available, and Required figures of such licenses, and the tracked software figures above them, can differ from those an earlier version showed. When a database is upgraded to 2026.1, the upgrade recalculates every license that is upgraded by a license of a different tracked software.

Compliance views and reports in the Default Workflow

A new 2026.1 database created with the Default Workflow (see Default Workflow Configuration) contains Web App views for following compliance across records. The views Non-Compliant Licenses, Compliant Licenses, and by Compliance are defined both for software licenses and for tracked software. Two shared Web App chart reports on tracked software, Software Licensing Compliance and Non-Compliant Software by Required, complete the set.

The supplied configuration contains no workflow rule that sends an e-mail when a license is not compliant; such a notification is something an administrator builds.

An upgraded database need not contain these views and reports, and an administrator may have changed them.