Snipe-IT Version
V8.4.1 (cloud)
How can we help?
Start first by saying that i've search the forum to the best of my knowledge and cannot find a reference to that anywhere surprisingly.
Is your feature request related to a problem? Please describe.
We have a lot of licences that are running on a floating model. The licence is used when the software is in use and released as soon as the software is closed. For example, we may have a 5-seat licence with 20 potential users.
Currently, this creates a tracking issue. We either:
- Manage two separate licences: one with the actual number of seats and a secondary one to represent additional users, or
- Enter an artificially high number of seats in the licence, which is inaccurate and misleading
Describe the solution you'd like:
Add a button or option in the licence details to define a "floating licence" type. When enabled, it would allow overcommitment of the licence (e.g., 5 seats with 20 assigned users).
This would make licence management more accurate and easier to track. In case of conflicts, it would also allow generating a clear list of users who can access the licence, which can be shared with the licence owner.
Describe alternatives you've considered:
Currently, to maintain accurate cost tracking, we manage a secondary licence to represent overflow usage.
For example:
- One licence with the real 5 seats and actual cost
- A secondary licence with additional "overflow" seats, set at 0$ cost
This workaround functions but adds complexity and reduces clarity in licence management.
Code of Conduct
Snipe-IT Version
V8.4.1 (cloud)
How can we help?
Start first by saying that i've search the forum to the best of my knowledge and cannot find a reference to that anywhere surprisingly.
Is your feature request related to a problem? Please describe.
We have a lot of licences that are running on a floating model. The licence is used when the software is in use and released as soon as the software is closed. For example, we may have a 5-seat licence with 20 potential users.
Currently, this creates a tracking issue. We either:
Describe the solution you'd like:
Add a button or option in the licence details to define a "floating licence" type. When enabled, it would allow overcommitment of the licence (e.g., 5 seats with 20 assigned users).
This would make licence management more accurate and easier to track. In case of conflicts, it would also allow generating a clear list of users who can access the licence, which can be shared with the licence owner.
Describe alternatives you've considered:
Currently, to maintain accurate cost tracking, we manage a secondary licence to represent overflow usage.
For example:
This workaround functions but adds complexity and reduces clarity in licence management.
Code of Conduct