IT explained
Why you should not use an administrator account every day
An administrator can change almost anything on a computer. That power is useful when you need it, but it should not accompany every email, website and download. A standard account for ordinary work gives you a valuable separation.
The short version
Use the right level of access for the job
A standard user can do ordinary tasks such as email, web browsing, documents and many application updates. An administrator can make broader changes, such as installing software for everyone, changing security settings and managing other accounts. The principle of least privilege means giving a person or program only the access it needs, for only as long as it needs it.
Using a standard account does not make malware harmless. An infection may still reach your own files or connected services. It does, however, avoid routinely presenting full system-changing rights to everything you open. Microsoft’s User Account Control guidance recommends a standard primary account, and the National Cyber Security Centre recommends separate everyday and administrator accounts for small organisations.
A simple example
Why the account you browse with matters
Imagine opening a convincing but malicious attachment. The harmful program may initially act with the permissions available to your signed-in account. If that account can change system settings or install software, the attacker may have more opportunities to interfere with protections or reach other users. A standard account reduces that starting level of access. Attackers can still try to exploit a software flaw, steal credentials or persuade you to approve an administrator prompt, so it remains one layer of a wider defence.
The same principle applies to cloud services. Someone who needs to read email and manage a Microsoft 365 tenant should normally have a daily account for email and a separate privileged identity for administration. The cloud administrator account should not be used for routine browsing and correspondence. Protect it with strong sign-in controls and monitor its use.
Windows permission prompts
What User Account Control does
User Account Control (UAC) is the Windows feature that asks before a program makes changes requiring administrator rights. This temporary step is called elevation. On a standard account, Windows normally asks for an administrator’s credentials. On an administrator account, it may ask only for approval. The exact prompt depends on device policy and the action.
The dimmed screen often seen behind a UAC prompt is called the secure desktop. It helps separate the genuine prompt from ordinary apps. Read the program name, publisher and action before approving anything. A legitimate-looking prompt is not proof that the program itself is safe. If a prompt appears unexpectedly, choose No and ask your IT support contact or investigate through a trusted route.
UAC is a useful boundary and warning, not a guarantee against malware, and it does not replace updates, device protection, backups or sensible account permissions. Avoid disabling UAC merely to stop repeated prompts. Repeated prompts may point to an unsuitable application or a workflow that needs fixing.
Keeping work practical
How to install software without living as an administrator
Keep your normal account standard. When a genuine task needs higher rights, an authorised administrator can approve that one action, install the software through a managed deployment process or make the change from a separate admin identity. This is different from leaving the user with permanent administrator rights. A support technician should explain what will be installed or changed and use an agreed support route; you should never give a stranger your administrator password or a one-time sign-in code.
Some older applications ask for administrator rights because of how they were written, not because every use genuinely needs them. JM Restart can investigate compatibility, permissions and vendor guidance rather than simply turning off security prompts or granting everyone full control of system folders. If an application truly cannot run under the agreed account model, we can document the exception, its owner and the compensating controls with the customer.
For remote work, follow our remote-support safety guide so you can verify who is asking for access.
For households and organisations
Set up separate access without locking yourself out
- Confirm a working administrator route first. Before changing an existing account to standard, sign in to another authorised administrator account and check that its recovery details work. Do not remove the only usable administrator access.
- Use a standard account for everyday activity. Keep email, browsers, documents and general applications there. Use administrative access only when a known task calls for it.
- Protect the administrator account separately. Give it a unique strong password or passkey where supported, use multi-factor authentication on cloud administrator accounts, and limit who knows or can retrieve recovery credentials.
- Review and remove unnecessary access. Check who has local and cloud administrator rights, including former staff, temporary contractors and support accounts. Remove rights when the role ends.
- Keep an emergency route. A business needs a controlled, documented recovery method that does not depend on one person being available. Test it without exposing a shared password in email or an unrestricted document. For eligible managed customers, JM Restart can help establish and maintain this route within the agreed support scope.
For managed Windows fleets, Windows Local Administrator Password Solution (Windows LAPS) can manage a unique local administrator password per supported device. JM Restart can deploy and manage it for eligible customers. Suitability depends on the supported Windows version, how devices are joined, where passwords are backed up and who may retrieve them. Windows Server Active Directory and Microsoft Entra ID are supported directory routes; Microsoft Intune can manage the policy where the customer has the appropriate setup and licence, but Intune is not required for every Windows LAPS deployment. A single shared local administrator password across many PCs is a poor recovery plan.
On a Mac: separate everyday and administrator access
macOS also has Standard and Administrator accounts. An administrator can manage other users, install apps and change wider settings. A standard user can install apps and change their own settings, but cannot add other users or change their settings. Apple recommends a standard account for everyday use when administrator rights are not needed. See Apple’s Users & Groups guidance and Mac security advice.
Macs do not use Windows User Account Control. A Mac may instead request an administrator name and password for a change that needs higher permission. Check what is asking and why before entering those details; an unexpected request is a reason to pause. If an older app repeatedly needs administrator access, investigate its requirements rather than leaving everyone as an administrator.
Before changing the only known Mac administrator to a standard user, create and test another authorised administrator route. Confirm the login and recovery details, and check who can unlock the Mac if FileVault is enabled. Recovery options depend on the way the Mac is set up, so do not assume an Apple Account alone will solve every lockout. For a managed Mac, coordinate any account change with its device-management policy. Read Apple’s login-recovery guidance and FileVault guidance before making changes.
Business baseline
What Cyber Essentials says about administrator access
The Cyber Essentials requirements for IT infrastructure, version 3.3 (April 2026), call for separate accounts used only for administrative activities. They should not be used for ordinary email, web browsing or other daily tasks. Organisations must also create and approve accounts, remove those no longer needed and remove special access when a role changes. These requirements include relevant third-party support accounts.
That is a useful baseline, but this page is not a certification checklist or a promise of compliance. The exact assessment scope and question set need to be checked for each application. JM Restart can help review access, implement agreed changes and prepare evidence; formal certification follows the appropriate assessment route. Read about our Cyber Essentials support.
Questions we often hear
A few useful distinctions
Is an administrator account safe if UAC is switched on?
UAC usually makes an administrator account run everyday programs without full rights until elevation is approved. That is valuable, but it is not the same as signing in with a separate standard identity. A person can still approve the wrong prompt, and a stolen administrator identity remains powerful. Separate accounts reduce the routine exposure of those credentials.
Does a standard user need IT every time they work?
No. Most everyday tasks should work normally. If routine work constantly asks for elevation, the application or deployment process needs review. A planned support route is usually less disruptive than leaving permanent administrator rights in place.
Is this only about Windows PCs?
No. The least-privilege principle also applies to Mac accounts, servers, cloud accounts, websites and business applications, although their controls and terminology differ. UAC itself is a Windows feature.
How JM Restart can help
For home and business customers, we can review administrator rights, set up separate daily and privileged accounts, check recovery access and implement agreed changes. This includes local Windows access and Microsoft 365 administrator roles where relevant. For eligible managed businesses, we can also plan Windows LAPS and a controlled emergency access route. This can sit within wider managed IT support and cyber-security planning. For households, see our home IT security guidance.
Changes to account roles should be planned and tested, especially on a device with only one known administrator. We will agree the scope before making changes.

