License consumption prioritization

10Duke Enterprise uses a license consumption prioritization mechanism based on type, consumption status, sharing priority, and expiry date to ensure efficient and fair resource allocation. While 10Duke Enterprise recommends using this default prioritization, custom priority logic can also be implemented. Contact the 10Duke Integration Support team for changes in the priority logic.

When selecting a license for consumption, 10Duke Enterprise prioritizes licenses based on the following criteria, in order:

1. Seat-based licenses (highest priority):

   • Consumed and reserved: sorted by the expiry date (longest validity first)

   • Consumed (but not reserved): sorted by the expiry date (longest validity first)

   • Reserved (but not consumed): sorted by the expiry date (longest validity first)

2. Use time-based licenses:

   • Consumed: sorted by the expiry date (shortest validity first)

   • Reserved (but not consumed): sorted by the expiry date (shortest validity first)

3. Use count-based licenses:

   • Consumed: sorted by the expiry date (shortest validity first)

   • Reserved (but not consumed): sorted by the expiry date (shortest validity first)

4. Valid licenses (seat, use time, or use count): sorted by the following, in order:

   • Sharing priority (based on how access to licenses is obtained):

     • Personal licenses

     • Organization licenses via the licenseConsumers group type

     • Organization licenses via the employees group type

     • Organization licenses via other groups types (custom)

   • Expiry Date:

     • Seat-based: longest validity first

     • Use time-based: shortest validity first

     • Use count-based: shortest validity first