Qintorava DocsProduct documentation
Guide

Allocate software and verify fulfillment

Manage product, package, bundle, entitlement, installation, and usage evidence.

Demo baseline · November 13, 2026
Download PDF

Prepare product and license records

Open Software asset management. Check product and edition, active package or bundle membership, license metric, available rights, effective dates, and target-device eligibility. Confirm that a deployment connector is configured if the workflow is expected to issue a device command.

Approve and fulfill

  1. Open the approved software request. Review the snapshotted packages, versions and approval requirements.
  2. Select the eligible device for the requested-for user. Select active matching entitlements for each item, enter required licensed units, and include meaningful verification evidence.
  3. Use the governed fulfillment action. For manual verification, record what was independently observed. For provider-backed deployment, follow the provider status to a terminal outcome.
  4. Verify the request, license allocations, installation CIs and typed relationships. Compare the requester-visible status to the fulfillment history.

Troubleshoot

Expired or wrong-product rights, non-device targets, and missing evidence can block fulfillment. If capacity changed during a concurrent request, refresh and check active allocations before retrying. If one bundle member is invalid, inspect all members and confirm that no partial fulfillment was persisted. Check actual usage telemetry before acting on reclaim candidates. See Entitlement fields and Installation fields.