The problem: A team of 25 developers needs administrator rights on their laptops to install Docker Desktop and a database tool. IT says, “No admin rights for anyone.” Security says, “Admin rights are fine for developers, with their manager’s approval.” The team lead hears two different answers, and the developers start using personal laptops.
Words used here: admin rights, also called local administrator, is the power to install or change anything on a laptop. Docker is a tool developers use to run applications in small, separate boxes on their own laptop. A personal laptop is one that the company does not own or manage.
Think of two managers and one master key
A contractor has to put shelves in a storeroom. He asks for the master key. One manager says, “Never the master key.” Another says, “Fine, take it for the day.” The contractor has a real job to do. He does not need a debate. He needs one answer. If he does not get it, he will prop the door open.
What it looks like at work
A new developer cannot install Docker Desktop, because the laptop blocks installing software. The developer asks IT. IT says the policy is that no developer has admin rights, because malware that runs with admin rights is far more powerful. The developer asks security, who say that admin rights are fine for developers with their manager’s approval. The developer goes back to IT with that answer. IT says, “Security does not run the laptops.” After two weeks, the developer is using a personal laptop with the client’s code on it.
- 11. Developer needsI need admin rights to install Docker.
- 22. Asks ITPolicy: no admin rights for anyone.
- 33. Asks securityFine, with your manager's approval.
- 44. StuckTwo answers. Who decides?
- 55. WorkaroundUsing my personal laptop instead.
Both sides are half right. IT is right that admin rights make an attack much stronger, and make laptops harder to support. Security is right that developers have a real need, and that a flat “no” will not stop the work. What is missing is one rule, with one owner, and safe options that meet the need without handing out full admin rights.
You will notice it when:
- IT and security give different answers to the same request.
- Developers ask “who decides?” and nobody is sure.
- Client code or data is found on a personal laptop.
- Admin rights are given to some people “just this once” and never taken back.
- Developers say, “It is easier to work around it.”
What exactly needs fixing
The first fix is not the policy. It is one answer, from one owner, that meets the need. This card shows the whole problem on one page:
IT and security give different answers on admin rights, so developers use personal laptops to get work done.
Developer laptops and the rules IT and security keep.
Client code and data end up on laptops nobody manages.
- Personal laptops
- Slow delivery
- Mixed messages
- Audit finding
- 11. Ask what is needed
- 22. Offer safe options
- 33. Name one decider
Who fixes it: IT head, security head
By when: one rule in 3 weeks
A blank copy of this card is in the Tools section.
Why it happens
- Two teams, two views of risk. IT sees support and attack strength. Security sees the business need.
- Nobody owns the rule. So each answers from their own side.
- The policy is an old, flat one. “No admin for anyone” was written before developers needed Docker.
- Nobody asks what the developer really needs. They ask for admin, and the need is a tool.
- Workarounds are easy. A personal laptop needs no approval.
- Exceptions have no end date. So they become permanent.
What happens if you ignore it
The work moves to places that nobody guards.
- Client code and data sit on personal laptops without protection or backups.
- Delivery slows, because developers lose days to getting an answer.
- Admin rights are given out informally, with no list of who has them.
- An audit finds personal laptops in use, and no clear rule.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Quite likely. It happens in most teams that write software. |
| Worst case? | Client code or data leaks from a personal laptop nobody manages. |
| What does it cost? | Lost days, an audit finding, and a client incident. |
| What if we wait? | More developers copy the workaround. |
| What does the fix cost? | One meeting, one named owner, and a few ready-made options. |
How to fix it, step by step
Say yes to the need, and control the way it is done.
- Ask what the developer really needs. Not “admin rights”, but “what do you need to install, and why?”
- Name one decider. One person or team who owns the answer, usually IT, with security as an advisor. Everyone else points to that person.
- Remove the need where you can. IT pre-installs Docker and the usual tools, so most developers never need admin rights.
- Offer time-limited admin. For rare cases: admin for four hours, on request, approved by a manager, and logged.
- Offer a separate dev machine. A virtual machine or a lab laptop where admin is allowed, but no client data and no direct access to the company network.
- Write one page. Who can get what, how to ask, how long it takes, and how long it lasts.
- Ban personal laptops for client work, clearly. Once the safe options exist, this rule is fair.
- Review the list every quarter. Who has admin rights, and do they still need them?
The picture shows the three safe ways. Most developers need only the first one.
Who to bring in: The IT lead (who owns the laptops), the security lead (who advises on risk), a developer team lead (who knows the need), and a manager who can approve requests.
Tools and templates
Admin rights options (example)
| Option | When to use it | Control |
|---|---|---|
| Pre-installed standard tools | Most developers, most of the time | IT manages the tools |
| Admin for four hours | A rare, one-off install | Manager approves, and it is logged |
| Separate dev machine | Work that really needs full admin | No client data, limited network |
| No admin | Everyone else | The default |
Blank finding card
| Field | Write here |
|---|---|
| What is broken | One line, in plain words |
| Where it is | The system, team, or process |
| What could go wrong | In one sentence |
| What it costs us | Money, time, a leak, lost trust |
| The fix | The exact action |
| Who fixes it | One name or one team |
| By when | A date, not “soon” |
Email to the IT lead and the security lead
Subject: One answer on admin rights for developers
Hi [name] and [name]. Our developers have heard two different answers about admin rights, and some are now using personal laptops for client work. I would like us to agree one answer. Could we meet for 30 minutes? I suggest we name one owner for the rule, pre-install Docker and the usual tools, offer four-hour admin on request for rare cases, and offer a separate dev machine for the few who need more. I will bring a list of what the developers actually need.
Field tip
Do not ask, “Should developers have admin rights?” Ask, “What do they need to install, and what is the safest way to give it to them?”
Words used in this chapter
- Admin rights: the power to install or change anything on a laptop.
- Docker: a tool that lets developers run applications in small, separate boxes on their own laptop.
- Personal laptop: a laptop the company does not own or manage.
- Time-limited admin: admin rights given for a few hours, then taken back.
- Dev machine: a separate machine used only for development work.