logo
6
Considering

It doesn't appear there is a way to modify a currently deployed (Status = Success) application and redeploy with the new settings. Delete and rebuild seems a bit awkward.

It doesn't appear there is a way to modify a currently deployed (Status = Success) application and redeploy with the new settings. Delete and rebuild seems a bit awkward.

3
Considering

Change “Installation Behavior” retroactively. For example, we have the problem that another piece of software (which was not previously installed on the client) must be excluded for an “Update Only” package. Currently, this requires regenerating the entire application package. The “Installation Behavior” field is grayed out.

Change “Installation Behavior” retroactively. For example, we have the problem that another piece of software (which was not previously installed on the client) must be excluded for an “Update Only” package. Currently, this requires regenerating the entire application package. The “Installation Behavior” field is grayed out.

2
In progress

Addtional column in Security Dashboard for CVSS v3.1 base score for the pending app update

Addtional column in Security Dashboard for CVSS v3.1 base score for the pending app update Would it be possible in a future update to include a column before/after Risk Score, maybe called "CVSS" and have it show the highest outstanding CVSS v3.1 base score for the app that needs updating? That way we can prioritise updating those apps that are 7.0 or above. I know the Risk Score is similar and obviously we should treat highest first, just think it might be a useful/nice addition if it was possible?

2
Planned

Ability from Pkgr to append an organizational description to all apps deployed to include "Any problems with installations please contact IT at XXX-XXX-XXXX or [email protected]."

Ability from Pkgr to append an organizational description to all apps deployed to include "Any problems with installations please contact IT at XXX-XXX-XXXX or [email protected]." This append would be nice if it was organizational so that every deployment gets the same thing appended to the description of the app so an end user can see it to remind them where to contact if any issues arrise. Or to know who is responsible for application updates to contact the correct department and so on.

2
In progress

Allow use of authenticator apps such as Microsoft Authenticator to protect "break glass" account

Allow use of authenticator apps such as Microsoft Authenticator to protect "break glass" account

1
Planned

Policy to limit when packages get updated for org, so that if a newly-released package has vulnerabilities or malware, you're not instantly hit with it. Let's say you can set a 7 day package age minimum before it gets promoted for your org as available

Policy to limit when packages get updated for org, so that if a newly-released package has vulnerabilities or malware, you're not instantly hit with it. Let's say you can set a 7 day package age minimum before it gets promoted for your org as available This is available in package managers (for software developers) like npm.

1
In progress

Being able to filter the view on custom applications to see deployed or not deployed apps

Being able to filter the view on custom applications to see deployed or not deployed apps I can see that the number of deployed apps is displayed (under custom apps) and counted, but can't click on it to drill down on those apps

1
Considering

TOTP for MFA on accounts

TOTP for MFA on accounts instead of using mobile numbers, please implement TOTP - this is a lot more viable for MSPs.

1
Considering

Make 2FA mandatory for all accounts, since its optionally its easy to forget to enable when you setup a new user

Make 2FA mandatory for all accounts, since its optionally its easy to forget to enable when you setup a new user It would be great to just enable it and let a user configure it the first time he logs into Pckgr.