Software Authorization

[RBosch01]

It would be great if some additional columns could be added to the Software Authorization page. One for "Comments" (a reasonably long text field) and another showing who made the last change to each particular item in the list, like you already have on the reports.

At the moment there's software on the list which someone has marked "red" (denied), but we have no idea why or who.

[bsmith_fujimi1]

Absolutely agree! Would love comments to track why it was approved, date approved, who approved it. Would like to be able to link tickets to the software authorization to track details of the request. Would like to be able to do conditional approvals (such as approved only for asset X, Y, Z or user A, B, C) and link to those records.

[sperigo]

Adding more items for categorization of software would greatly enhance enterprise customers. For example, have custom fields for the software items and/or on the Software Authorization, add another field for items like opensource, freeware, paid software, etc - this will help is tracking various types of software.

Please add this to the wishlist.

[msudol]

The current iteration of this is too simplistic for enterprise use. Within thousands of devices and softwares to simply have a global allow/deny does not account well for software that fits within a group-based exception policy.

While the suggestion for customizable status is preferable, it should be rather easy to add in a few new status options in the interim. Might I suggest just adding a "yellow" option for "Monitored" as a very quick half-step to a more robust improvement.

Approve, Monitored, Denied, Neutral

This would at least give us a way to watch for the proliferation of semi-restricted software that may be required by specific users and groups.

[Lanswiffer]

msudol wrote:
The current iteration of this is too simplistic for enterprise use. Within thousands of devices and softwares to simply have a global allow/deny does not account well for software that fits within a group-based exception policy.

While the suggestion for customizable status is preferable, it should be rather easy to add in a few new status options in the interim. Might I suggest just adding a "yellow" option for "Monitored" as a very quick half-step to a more robust improvement.

Approve, Monitored, Denied, Neutral

This would at least give us a way to watch for the proliferation of semi-restricted software that may be required by specific users and groups.

Great idea, please do this Lansweeper!

[Esben_D]

Features on the customer wish list get development prioritization based on a combination of customer demand and difficulty to implement. As such we can unfortunately not give an estimated release date when this update may get released. However, letting us know you would like to see this feature to be implemented into Lansweeper does add weight to this feature request.

[philou92]

Agree. It should be more efficient to choose ourselves the values which could be implemented with a specific colour or item associated with each value.

[tech4him]

philou92 wrote:
Agree. It should be more efficient to choose ourselves the values which could be implemented with a specific colour or item associated with each value.

Yes, this would be ideal as it could better match the semantics used by each organization. +1

[RBosch01]

Maybe it would be better to have a set of pre-defined values (Approved, Not Approved, etc.), but also these and allow up to X additional values to be created or renamed in the Configuration options. That way, Lansweeper users can set them as they wish.

[tech4him]

While on the topic. Allowing for more categorization would indeed be helpful. In our case, we would have:

- Approved (full support)
- Allowed (limited support)
- Allowed (no support)
- Not Approved
- Malware/Adware - Immediate Removal