Colour theme
Book a consultation

Limiting administrator access on staff computers

Use standard accounts for daily work, provide an installation process and test specialist software before removing permanent administrator rights.

Colleagues working on laptops at a shared office table.

An employee needs a printer driver, so someone makes their account an administrator. Months later, that permission is still there, although the original task is finished.

Local administrator rights allow changes affecting the whole computer. If that employee opens a malicious attachment, the malware can use the same rights to install itself or turn off security software. Keep ordinary work on standard accounts and give staff a practical way to request the installations and settings they need.

Separate daily work from administration

Email, browser use and most business applications don’t require a permanent administrator account. Local device administration is also separate from administering Microsoft 365, Google Workspace or a server. Review each type of access on its own.

Microsoft’s User Account Control guidance explains the distinction: a standard user normally needs administrator credentials to approve an administrative change, while an administrator can approve the change themselves.

That extra checkpoint limits some system changes. It doesn’t make a standard account immune to malware, phishing or theft of files the user can already access. Keep patching, endpoint protection and recovery controls in place.

Inventory accounts before removing permissions

Have IT review local administrators on Windows computers and administrator accounts on Macs. Include old setup accounts, vendor access and accounts used by support tools.

For each account, record who controls it, what needs the permission and how it can be recovered. Test a protected administration method before removing staff permissions. Otherwise, you can leave a remote employee with a computer no one can maintain.

Check how encryption recovery keys and device-management access are held. The business needs a recoverable support process if a provider changes or an administrator leaves.

Give staff an installation process that works

Explain where to request software, what information to provide and how urgent requests are handled. Ask for the application’s name, what it’s for and where the official download comes from.

IT can deploy software it has checked, install it during a support session or use an elevation tool that grants administrator rights for one specific task. Availability depends on your devices, management setup and licences.

People doing technical work may need a separate administrator account or controlled temporary elevation. Record the reason, scope and review date. Use that access for the task and return to the standard account for browsing and email.

Test specialist applications with a pilot group

Start with a few representative users. Test application launches, updates, printing, scanning, integrations and work done away from the office.

If an application fails, ask its vendor which permission it needs. A supported update or narrowly defined folder permission may solve the problem. Avoid granting broad write access to system folders as a quick fix.

For equipment controlled by a specialist supplier, coordinate changes with them. Record an exception when you can’t remove the permission immediately, with an owner and a plan to review it.

Protect the remaining administrator accounts

Don’t reuse one local administrator password across the fleet. Protect privileged credentials and restrict who can retrieve them. Log their use where your management system supports it.

Windows LAPS can manage and rotate local administrator passwords on supported Windows devices. IT must configure the storage and retrieval permissions correctly; installing the tool alone won’t do it.

Work out how you’ll handle this on Macs and other devices too. Check emergency administration access without making a shared password the routine way to support staff.

Roll out and review the change

Tell staff what will change before switching their accounts. Give them the request process and check the pilot results before extending the change.

Review exceptions when roles change, applications are replaced or devices are reassigned. Remove access as soon as it’s no longer needed, so a permission granted for one old installation doesn’t carry over to the next employee’s setup.


Featured Image Credit