18 Nov Employees Shouldn’t Have Administrator Access
Administrator access often starts with one request. An employee needs to install a printer, update a specialist program, or change a setting on their computer. Giving them administrator access gets the job done. The problem is that the access usually stays after the request has been completed. From then on, the employee can approve other software installations and make changes that would normally require help from IT. If they install the wrong program or someone takes control of their account, those permissions can also be used to change the computer. For everyday work, employees should use standard accounts. Administrator access should be kept for tasks that require it.
What administrator access allows someone to do
Administrators have more control over a computer than standard users. They can install or remove software, add hardware drivers, manage user accounts, change system settings and permissions, install background services, and modify some security settings. Mac administrators have similar abilities, including installing software, managing users, and changing settings. Administrator access should therefore be limited to people who genuinely need it. Local administrator access only applies to the computer and is different from Microsoft 365, Google Workspace, network, or server administrator access. Each type of administrator access should be reviewed and managed separately.
Why permanent administrator access increases your risk
Software approved with administrator access can make significant changes to a computer, creating greater risk from malicious or untrusted programs. Standard accounts are safer because administrator approval is required, allowing IT to review software before changes are made.
Standard accounts are suitable for everyday work
How to manage software installations without permanent administrator access
Staff can still get software installed and updated without keeping administrator rights.
- Let IT install approved software. This also gives them a chance to confirm that the installer came from the software company and that the requested version is supported.
- Use managed software deployment. Businesses with managed computers can send approved applications and updates to employees without asking each person to run an installer.
- Approve individual requests. An employee can contact IT when an installation requires administrator approval. IT can review the request and enter the required credentials without giving the password to the employee.
- Provide time-limited administrator access. Some roles need to install or test software as part of their work. Give those employees a separate administrator account that is enabled only for the approved task, then disable it afterward.
- Create a separate administrator account. Employees who regularly perform approved technical work can have a separate administrator account. They should continue using their standard account for email, browsing, and normal work. The administrator account should only be used when a task requires the extra permissions.
- Who should have administrator access? Administrator access should be limited to IT staff, IT providers, and approved technical employees who genuinely need it. Everyone else, including business owners, should use standard accounts for everyday work. Administrator passwords should be protected, never shared, and unique for each computer.
How to remove administrator access safely
Do not remove every administrator account at once. Someone still needs a working way to manage and repair each computer.
- Check which employees have administrator access. Review the local Administrators group on every Windows computer and the administrator users on every Mac. Include old accounts, shared accounts, vendor accounts, and accounts created during the original setup.
- Confirm why each person has it. Ask what tasks require administrator access. A clear business need should exist for every account that keeps the permission. Needing to update one application occasionally does not require permanent access.
- Make sure IT has a working administrator account. Confirm that your IT team or provider can sign in with a protected administrator account before removing permissions from employees. Test the account on each device. This prevents the business from being locked out of its own computers.
- Test important software. Check the programs each employee needs for their job. Confirm that they open, update, and work correctly when the employee uses a standard account. Any application that fails should be reviewed before administrator access is removed permanently.
- Change the employee’s account to a standard account. Once the computer has been checked, remove the employee from the local administrator group or change the account type. The employee should then sign out and sign back in so the new permissions apply correctly.
- Tell staff how to request an installation. Give employees one place to contact when they need software installed or a setting changed. Explain what information to include, such as the program name, the reason it is needed, and the official download page.
- Review access when roles change. Check administrator access when an employee changes jobs, receives new responsibilities, or leaves the business. Include it in your regular access reviews as well.
Robert Brown
18/11/2026
Related Articles:
Shared Logins Are a Security Risk for Your Business
How often should a small business check its IT?