Keep Everyday Work Separate From Computer Settings

Most tax work does not require administrator rights. Preparing returns, reviewing workpapers, using email, and browsing client portals should normally happen from a standard user account. The Cybersecurity and Infrastructure Security Agency’s current performance goals say ordinary user accounts should not have administrator privileges and that administrators should use separate accounts for work outside the administrator role. That separation limits what one stolen password or malicious attachment can change.

This matters in a small accounting office because the same computer may hold tax software, document tools, email, and access to cloud storage. An account with administrator rights can install software and change security settings. If that is also the account used all day, a bad download or convincing phishing message gets a wider path than it needs. The goal is not to make routine work difficult; it is to reserve elevated access for the few tasks that actually require it.

The IRS guide Safeguarding Taxpayer Data tells tax professionals to limit taxpayer-data access to people who need it, give each person unique credentials, keep software current, and avoid unnecessary applications. Separate administrator accounts put those recommendations into a practical work computer rule: employees use named standard accounts for daily work, while an authorized person uses a different named account for approved installations, updates, and configuration changes.

Today, ask your IT provider to check one work computer while the regular employee is signed in. Record whether that account can change important computer settings, which other accounts can do so and who owns them. Do not remove access blindly. Confirm that tax, payroll, scanning and document software still work with ordinary staff access, and ask the software provider about any task that needs extra permission.

If an application needs administrator approval for an update, make that a controlled step instead of leaving every user permanently elevated. Protect the separate administrator account with a unique password stored in the firm’s approved password manager and multifactor authentication (an extra check when you sign in) where the platform supports it. Avoid shared administrator credentials, document who may approve changes, and remove old vendor or employee administrator accounts that no longer have a business purpose.

This is a focused risk reduction, not a complete written security plan and not a reason to interrupt return preparation without testing. Start with one work computer, document any software exceptions, and expand only after the workflow is proven. A standard daily account plus a separate administrator account is a quiet control that can reduce the impact of an ordinary mistake without changing how the firm serves clients.