Software Deployment

Sounds like you're trying to do this in the User Portal > Downloads section. Is that correct? - ondrar 6 years ago

Unfortunately, setting access through Roles is pretty much all or nothing per module (Write/Read/Hide), but in 8.0, they added the ability to limit Roles to device labels, which would allow people in a given Role to act ONLY on devices in that label, so you may be able to make use of that. But again, unfortunately, it's only for Device labels, which would mean the Jr. Admins would be able to use any script on a small subset of devices, instead of a small subset of scripts on any device.

Here's what I do, for another idea. Instead of giving all our techs full administrator access, I have them in a Role with Read rights to most everything. They can see everything (and maybe you don't even want that), but can't edit it.
If they need to run a Managed Install or Script on a computer, I have manual labels set up that are tied to those. The tech applies that label to a computer, and that action is scheduled for that computer. (For MIs, they can even force an Inventory to have it run now.)

Perhaps you could use that method, and only make labels for the MIs and Scripts you want the Jr. Admins to be able to use. Full Administrators would still be able to add computers directly to MIs or Scripts, which would allow them to execute tasks outside the Jr. Admin scope.

Hopefully that helps, or gives you some ideas, since KACE doesn't have exactly what you're looking to do.

You may also want to see if there's a feature request for more granular organization or something like that at kace.uservoice.com. - ondrar 6 years ago