Skip to main content

How Does Your Org Handle Responsibilities for Jamf?

  • Nov 16, 2026 10:54 AM UTC
  • 1 reply
  • 32 views

mhend1982
Forum|alt.badge.img+3

Hello everyone,

I’m curious how other organizations handle Jamf ownership, administrator access, and peer reviews, particularly for the engineers responsible for managing the environment day to day.

I’m currently our only certified Jamf Engineer. About 10 months ago, ownership of Jamf moved to our another team. Since then, certain tasks involving our primary Apple Business account have required me to go through that department, even when those tasks directly support my responsibilities.

For example, it took nearly 30 days to renew the push certificate in our development environment. Thankfully, this wasn’t production, but it raised concerns for me about how we would handle something similar in Prod.

We have separate Apple accounts for our primary administrative functions, production, and development. The primary account is considered a “break glass” account, and my request for access was declined because of its elevated permissions, including the ability to release devices.

I understand the need to protect privileged accounts. What I’m trying to work through is how to balance those controls with the access engineers need to maintain the environment and respond to issues. I’d be interested in hearing whether other teams use delegated permissions, privileged access tools, or a documented emergency access process.

I’m also curious how you handle peer reviews. Our Jamf production changes are reviewed by colleagues who are knowledgeable in their own areas but don’t have much Jamf experience. I value their input, although sometimes the review becomes more about explaining Jamf functionality than evaluating the risk of the change.

A recent example was a request to deploy one app to one device for an employee’s accessibility needs. The reviewer questioned why I hadn’t created a Smart Group. I explained that I had scoped the app directly to the device by serial number and used an “ADA” category to organize it. We already have a large number of Smart Groups, so I’m trying to avoid adding unnecessary ones while identifying older groups we can retire. That led to a longer discussion than I expected for a small deployment.

For context, I hold Jamf 100, 170, 200, and 300 certifications, and I’m working toward 400 as time permits. I certainly don’t believe certifications are required to be a capable Jamf administrator. My concern is making sure responsibility, access, and technical review are aligned so the people supporting the platform can do their jobs effectively.

I enjoy the work and respect my colleagues. At times, though, I feel accountable for the environment while depending on others to complete some of the tasks needed to support it.

How does your organization approach this?

Who owns Jamf, and what access do your day-to-day engineers have? How do you manage privileged Apple accounts and certificate renewals? And do Jamf changes require review by someone with Jamf experience, or do you use a broader infrastructure review process?

I’d appreciate hearing what has worked well for other teams, especially in larger or healthcare environments. I’m hoping to bring back some practical ideas for clearer responsibilities and a smoother support process.

I look forward to hear from others on how you use Jamf based on certs, knowledge of the platform, etc.

Thanks, everyone!

1 reply

woaikonglong
Forum|alt.badge.img+9
  • Jamf Heroes
  • Nov 16, 2026 4:57 PM UTC

We are a two person IT team for our 3K-12, but the IT Director probably doesn’t even know his sign-in for Jamf and hasn’t touched it since probably 2015.

 

When I started it was a team effort for Jamf between him and another guy until the other one retired, took away IT Director’s keys, trained me on Jamf in an afternoon and made me the sole admin on his last day. Not my dream story of how to begin an IT career with a paleontology background, but it worked.

 

I am also our school’s only Jamf certified in anything (200 was my last), and had to fight for the ability and time to do so. We keep our instance very simply managed, so it was deemed not required. Jamf is solely under our IT Department, so luckily I only have to deal with the business office when I have to pay for a renewal. All app and device purchases and requests also go through us as a final step.

 

As the sole Jamf admin, and also wearing a number of other hats at our school, I have a Google Folder of recipes for when I finally go off the deep end and quit win the lottery and move on so they are not left stranded. IT Director knows the recipe books exist and knows that my account should just be suspended if I “get hit by a bus,” so a new admin can easily get what they need. In my recipes I have a simple Title of what it is. A “When” to indicate how often and if it is as needed or recurring, and it has a smartchip that links to a Google Calendar event that I update as needed if it is recurring so that I have reminders built into my system. There is then a Procedure header where I walk through what needs to be done, links to other pertinent documents or pages, and links to the password document and which header to look under there. Itis *hopefully* dummy-proof.

 

This has allowed me to make sure things have gotten done while I was on a J-Term trip. I can send the document to the IT Director if needed (haven’t had the need). I am able to set reminders so far in advance of my Google events to ensure that I have plenty of time to complete the task. The biggest thing I have going for me is that the locus of control is in my hands, and my department. The only person I am waiting on is myself in 98% of cases. I have access to our accounts for Apple School Manager, I am also the person who releases devices, and does all the renewals and purchases of apps. Not having access would greatly prohibit my ability to get things completed efficiently and in a timely manner. We do not have delegated privileges, but only because no one else seems to know how to log in, or how the systems work after the other guy retired and things kept *magically* working.

 

We do not have a peer review process. I just live cautiously and do everything in Prod! 😅 I have a small set of devices that are seldom used that I will use as a test set when doing something strange. I’ve found that trying to review with my director who is quite removed from Jamf at this point starts to lead down conversations of “Do we really need this product?” type lines that scare me so I only ask for input seldomly at this point because he does not value my work time the way I do.