Software Asset Management

On this page

Software Asset Management (SAM) connects three kinds of record: the software products that inventory finds, the software your organization decides to manage, and the licenses that entitle you to use it.

The three levels

  • A Software Product is a catalog entry: product name, manufacturer, version, platform, suite, group, and category. It is what inventory reports finding. Alloy Navigator does not maintain this catalog: its entries arrive through the AlloyScan and Alloy Discovery synchronizations.
  • A Tracked Software item is the software your organization decides to manage. It has no software-specific fields of its own; it groups products. One Tracked Software item can cover several product versions or editions.
  • A Software License is an entitlement. It points to no more than one Tracked Software item. Nothing links a license to a product directly: every link between a license and a product runs through the Tracked Software item. The license's quantity is the only entitlement figure.

A product leaves the catalog only when no Tracked Software item maps it and no discovered installation names it. Removing a product from a Tracked Software item removes only that mapping and keeps the product; the next AlloyScan or Alloy Discovery run then deletes a product that nothing refers to any more. Alloy Navigator has no command that deletes a discovered installation. An AlloyScan or Alloy Discovery load can remove a computer's installations of products that are missing from the software it loads for that computer. Retiring a computer keeps its discovered installations, so their products stay in the catalog. Deleting a computer, a hardware item, or a product removes the installations that name it.

Installations and allocations

A discovered installation pairs a software product with the computer or hardware item it was found on. Only installations on computers and hardware that are not retired count in compliance and usage figures. When a member of a suite is found on a device, the suite's parent product is added to that device too, and when a product becomes a member of a suite, the parent product is added to every device that has the product.

An allocation links a license to a computer, a hardware item, or a person. Allocations are made by hand or by automatic allocation; see Allocate Software Licenses. Allocations of retired licenses, and allocations to retired computers, retired hardware, or inactive persons, are not counted.

Policies and tracking

A licensing policy's tracking type, when it has one, is one of four values: By Device, By Device Owner, By User, or None. The policy name is mostly a label; the tracking type is what changes how usage is counted:

  • Under By User, usage counts the license's allocations to persons who are not inactive.
  • Under By Device Owner, usage counts the distinct owners of the allocated computers and hardware that are not retired.
  • Under By Device, or when the policy has no tracking type, usage counts the license's allocations to computers and hardware that are not retired.
  • Under None, every usage count of the license is zero.

On a Software License form in the Web App, Allocate offers only allocating to a person under a By User policy, and allocating to devices under any other policy; see Allocate Software Licenses.

When a database is created, it gets five licensing policies that have no tracking type. A policy that has no tracking type is not treated as None when compliance is computed. Adding a licensing policy sets By Device on every policy that has no tracking type.

A new 2026.1 database created with the Default Workflow (see Default Workflow Configuration) contains the licensing policies below, and each has its tracking type set in the supplied configuration. The five policies every database gets are among them, marked in the last column; the other eight come from the supplied configuration.

Policy Tracking type One of the five every database gets
Per Installation By Device Yes
Named Computer By Device Yes
Per Named User By User No
Per User By User Yes
Per Device Owner By Device Owner No
Site License None Yes
No License Required None Yes
Concurrent None No
Per Database None No
Per Organization None No
Per Processor None No
Per Seat None No
Per Server None No

An upgraded database need not have this content, and an administrator may have changed it.

Beyond its tracking type, a policy matters for compliance only in three cases: the No License Required, Site License, and Named Computer policies.

A license whose policy is No License Required is always compliant: no other compliance check applies to it, and it stays compliant after its expiration date. The supplied configuration sets that policy's tracking type to None, so every usage count of such a license is zero. When any license of a Tracked Software item has a policy that tracks None, the item's summary figures, such as Allocated, Used, Available, and Required, are zero as well.

The Per User policy, whose tracking type is set to By User in the supplied configuration, suits a license that lets one person install the software on several of their devices: the license is allocated to the person rather than to each device, and its usage counts persons. Under By User, the installations per user, allowed CPUs, and allowed CPU cores restrictions are not checked.

A license can also carry restriction rules, which are what a policy is enforced by. There are eight kinds: organization, location, device name, device owner, user, installations per user, allowed CPUs per license, and allowed CPU cores per license. How the policy, the tracking type, and the restrictions decide whether a license is compliant is covered in License Compliance. In the Web App, the Software License form shows the license statistics and the restriction rules, which can be added, changed, and deleted there.

Licensing policies and their tracking types are maintained in the Settings App; see Classification.

Software Asset Management in the Web App

The Web App's Software Asset Management section holds four lists:

List Holds
Software Products The software catalog
Software Licenses Licenses
Tracked Software Tracked Software items
Discovered Installations Installations found on computers and hardware

Software Products and Discovered Installations are catalogs you cannot create records in: both lists switch off New and workflow actions.

Opening a row on the Discovered Installations list does not open a record for the installation: it opens a license-allocation view of the record that hosts it.

Create a Tracked Software item

  1. Open the Tracked Software list and its New menu, or use the header's New... menu.
  2. Choose the action that creates a Tracked Software item and complete its form.

The header's New... menu lists the create actions you used recently and has a submenu of the classes that have create actions. Each time you open the list's New, it loads the create actions of the class: it shows Loading... while it does, and No Actions when the class has none. Grouped create actions appear as nested submenus.

Create a software license

In a new database created with the Default Workflow (see Default Workflow Configuration), the Software Licenses list offers the following procedure:

  1. Open New Software License and choose Software License.
  2. Complete the Create a Software License form and submit it.

In the form's License Compliance Rules section, Policy is set to Per Installation and shown with (Tracking: By Device). That preset belongs to this form only and does not apply to licenses created in other ways.

Retired Tracked Software and licenses

The retire and unretire actions below are those of a new 2026.1 database created with the Default Workflow (see Default Workflow Configuration). An upgraded database need not have them, and an administrator may have changed them.

Retire Tracked Software or a license

  1. Open the Tracked Software item or the software license in the Web App.
  2. In the Actions panel, choose Retire Software for Tracked Software or Retire License for a single license.
  3. Complete the Provide a Reason form, which offers Comment, Time Spent, and Attachments, and click Submit.

Retiring Tracked Software has these effects:

  • the Tracked Software item is Retired;
  • every Software License of the item is Retired, and its activity reads Marked as retired;
  • every asset associated with those licenses is Retired, with the retirement date set to the time of retirement.

Retiring a single license also retires that license's associated assets.

The only action a retired Tracked Software item offers is Unretire Software; a retired license offers only Unretire License, and a retired asset only Unretire Asset. Most fields of a retired license are read-only. A retired license counts nothing: its quantity and every usage count are zero. Retired Tracked Software items and licenses are not offered when you pick a Tracked Software item or a license, for example in the Tracked Software field of the Create a Software License form.

Return retired software to stock

  1. Open the retired Tracked Software item or software license.
  2. Choose Unretire Software or Unretire License.
  3. Complete and submit the form:
    • Unretire this Tracked Software offers Stock Room, Comment, Time Spent, and Attachments.
    • Unretire Software License offers Stock Room and Comment.

For Tracked Software, the item, the licenses retired with it, and their associated assets become In Stock. For a single license, that license and its associated assets return to stock.