/build/static/layout/Breadcrumb_cap_w.png

Restrict Managed Installation and Scripts by User

Is there a way to restrict the managed installation and scripts available to the logged in user? For example, I want to create some "Power Users" that can run certain scripts and install certain software, but I do not want them to have access to the whole script and managed installation library. I am not seeing a way to restrict what they can view.

2 Comments   [ + ] Show comments
  • Sounds like you're trying to do this in the User Portal > Downloads section. Is that correct? - ondrar 6 years ago
    • No, in the Admin portal for junior admins. We want them to have access to some scripts and managed installs plus all the Inventory features, just not everything. - taylora 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

Answers (0)

Be the first to answer this question

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ