Is there a built in way to grant access for site admins to add/modify printers, packages and scripts that does not give them the same access to ALL printers, packages, and scripts?
I work at a University and we are attempting to find a way to allow separate departments to have their own access to 'their' stuff in JAMF without impacting all other departments. I know this is possible by creating separate instances, but also trying to avoid that.
Thoughts? If the answer is you must create a process internally, what have other larger institutions done?