Securing Shared Devices, Access Rights and Staff Offboarding
Understand the practical access controls that protect client records when employees change roles, use shared equipment or leave a firm.

Xian Hui
9 November 2026 · 4 min read

In brief
How can an accounting practice control staff access on shared devices and when someone leaves?
Use named accounts and give staff only the access their assigned work requires. Separate access on shared workstations, review permissions when roles change and set end dates for temporary access. When someone leaves, transfer necessary files, remove access, revoke sessions, collect devices and record completion.
What you'll learn
- Recognise excess permissions and shared identity risks
- Apply account and device controls during staff changes
- Describe a basic quarterly access review
Securing Shared Devices, Access Rights and Staff Offboarding
A staff member finishes a three-month assignment for one client and joins another team. Their old client-folder permissions remain unchanged. Months later, the employee can still view information unrelated to their current work. Nothing dramatic needs to happen for that to be a control weakness.
Good access management follows the employee's actual responsibilities. It applies when someone joins, changes role, works on a temporary assignment or leaves the practice.
Why should every person have their own account?
When several employees use one login, activity cannot be reliably attributed to an individual. A shared account can also remain active after one person leaves, and changing its password disrupts everyone else who uses it.
Create named accounts wherever the service permits them. Give administrative privileges only to people responsible for administering the system. Where a shared workstation is unavoidable, use individual operating-system sessions or another supported method to separate staff access. Do not assume that a shared office location makes shared identity safe.
For related sign-in controls, see Passwords, Passkeys and Multi-Factor Authentication for Accountants.
This approach is consistent with the access-control themes described in ISO/IEC 27002:2022. The standard's public overview supports risk-based controls, but it is not a certification checklist for an individual employee.
What is least privilege in an accounting team?
Least privilege means giving a person the access needed for assigned work, rather than the widest possible access. The decision should also consider what the person can do, not only what they can view.
An accounts assistant may need to read supplier invoices for an assigned client. They may not need to edit bank details, delete archived records or access every other client. A partner may have wider responsibilities, but access should still be reviewed and justified.
A useful permissions register includes the user's name, system, assigned client or department, access level, business owner and review date. It should be understandable without relying only on technical role names such as 'editor' or 'administrator'.
What changes when a staff member leaves?
Offboarding is not limited to collecting a laptop. The firm should review email, accounting applications, cloud storage, document-sharing links, virtual private network connections, password vaults, mobile sessions and integrations connected to the person's identity.
Use this example departure checklist:
| Step | Action |
|---|---|
| 1. Confirm the departure | Confirm the person's last working day and responsible manager. |
| 2. Transfer work | Transfer ownership of necessary client files and tasks to authorised colleagues. |
| 3. Close accounts and sessions | Disable or remove relevant accounts and revoke active sessions in line with policy. |
| 4. Remove shared access | Remove access to client folders. Change any shared password or credential the leaver knew, remove their MFA devices and check for mailbox forwarding rules. |
| 5. Collect devices | Collect managed devices and check that any permitted local copies are handled correctly. |
| 6. Complete the record | Record completion and resolve any exceptions. |
Different systems may require different actions. Disabling email alone does not always revoke a separate application's session or token.
Include connected services in the review, as discussed in Reviewing Cloud Applications, Integrations and Vendor Access.
How often should access be reviewed?
Use a risk-based schedule. A quarterly review is a workable example for a small practice, rather than a legal requirement. High-risk systems and role changes may justify more frequent checks. At each review, compare system permissions against the current staff and client assignment lists.
The NIST small-business quick-start guidance encourages firms to understand their assets and risks rather than relying solely on tools. A permissions review gives the manager a concrete way to do that.
What about temporary access?
For a deadline assignment, record why access was granted and when it should end. A reviewable expiry date is better than leaving permission in place indefinitely. If a manager believes an employee needs 'all clients' access, ask which duties require it and whether a narrower role is available.
Key takeaways
- Individual accounts improve accountability and make access removal easier.
- Review both visibility and the ability to modify or export client information.
- Treat role changes and departures as access-control events.
- A simple permissions register can reveal excessive access before it becomes an incident.
Last source check: 9 November 2026.
Next in the course: Classifying and Sharing Client Records Safely
Sources
Frequently asked questions
This information has been prepared for general informational purposes only and is not intended to be relied upon as accounting, tax, or other professional advice.


