interaction design – How to make licensing easy to use when technology and resources are limited?

I'm building a portal for business users or those with a single license to manage their account for a 3D CAD application.

Due to weak resources and lack of information about the project, the architecture was built in such a way as not to allow the awarding of a license. Thus, whatever the existing license, it must always be attributed to a user.

If you have 150 licenses, all licenses will be allocated to the account owner or member.

Whenever someone is not assigned, it is automatically assigned to the owner.

Preliminary tests with MVP:

  • Confusion with the license can not be disconnected from someone's
  • No indication that the license is unallocated.
  • It does not inform the administrator (account holder) that the license can be given to anyone.
  • When a team is big, it's even more confusing (I tested myself and I was lost).

Now, the second architecture solution would require significant changes (higher development costs):

In order for a license to display as unallocated, it should be floating, so that it still belongs to the company and is therefore used by no one.

Key complications of this solution: the software uses a security dongle and has many security triggers that require the unlocking of the user (not only for the first time, but every 6 months, as well as for the renewal of l & # 39; subscription).

If the license is not awarded, it means that the user will get another barrier that did not exist before (worse experience) and will not be able to use the software he bought, unless he assign himself. Including single-license users who do not have a team, they will need to assign the license via a portal in order to allow themselves to use it, in addition to activating it.