Contents
A clerk changes teams, but their old matters remain visible. An outside expert finishes a report, yet a shared folder stays open. A client changes contacts, while the earlier contact still has portal access. Each change calls for a fresh look at permissions.
A law firm access review checks who can reach firm information, what they can do, and whether that access still serves an approved purpose. It should end with verified changes and a record of unresolved issues.
This guide provides a practical checklist for small and midsize firms in Canada and the United States. The suggested schedule and workflow are firm policy choices. Adapt them to applicable professional rules, privacy obligations, client terms, and the systems you use.
What a law firm access review covers
Review both the person and the information. A current employee may need narrower access after changing roles. A former contractor may still have a guest account. A correct matter team can sit beside a document folder shared more broadly.
Separate sign-in from permission
Authentication checks who is signing in. Authorization controls what that person may reach or change. Multifactor authentication helps protect sign-in, but it does not establish whether a user needs every file their account can open.
The Canadian Centre for Cyber Security recommends unique accounts, limited admin privileges, and the minimum access needed for assigned tasks. This last concept is called least privilege. Its access-control guidance also recommends managing accounts throughout their lifecycle.
Apply that principle during a law firm access review by asking what work supports each permission. A job title alone rarely explains access to a particular sensitive matter.
Review the available actions
Record more than whether someone can open a file. Check whether the system separately controls reading, editing, downloading, sharing, deleting, billing, and administering access. Some tools combine these actions into one role; others separate them.
Describe the actual control available. If a tool cannot limit an action as required, record the gap and obtain a decision about a safer setup. Avoid claiming a permission exists because the firm would like to use it.
Set the scope and assign decision makers
Start a law firm access review with a defined list of systems and people. Include your practice management platform, email, document storage, client portal, billing tools, and external collaboration sites. Add devices or local storage where the review requires them.
Ask staff where they share information outside the main platform. An expert workspace or a temporary upload folder may sit outside the admin’s usual account list. Record these locations before treating the review population as complete.

Give each decision an owner
Assign a coordinator to collect records and track follow-up. The responsible lawyer should decide who needs matter information. An authorized system administrator, called an admin here, should make technical changes. Someone should then verify the result.
In a small firm, one person may hold several roles. Still record who made each decision and who applied it. Seek a second review for changes with a large effect where staffing allows, especially when an admin proposes retaining their own broad access.
Protect continuity while narrowing access. Confirm who will receive urgent messages, complete assigned tasks, and handle upcoming deadlines. A law firm access review should leave an authorized person able to carry the work forward.
Use a repeatable access review checklist
Use the following sequence as a starting point. For each step, record the finding, decision, owner, and evidence of completion. Work through urgent exposures promptly rather than waiting for the entire checklist to finish.
Prepare the law firm access review register
Collect current user lists, team memberships, permission settings, guest invitations, sharing records, and connected application lists where available. Date each export or screenshot and note its source. Keep the review material in a restricted location.
Your register needs enough detail to explain a decision without copying the underlying client file. Use matter references and links to restricted evidence. Avoid putting sensitive matter names into broadly visible task titles.
The table below shows a compact record structure for a law firm access review. These fields are suggested choices, not a prescribed regulatory form.
| Record field | What to capture |
|---|---|
| Account and system | Named user or application, account identifier, and platform |
| Information and action | Matter or resource reference and actual permission level |
| Business need | Current assignment, purpose, and approving owner |
| Decision | Retain, reduce, remove, or investigate |
| Follow-up | Change owner, target date, and any approved expiry |
| Verification | Test result, verifier, date, and evidence location |
Step 1: Match accounts to current people
Compare accounts with current staff, contractors, temporary workers, and approved external collaborators. Check duplicate accounts, old invites, leave arrangements, and people who have changed roles. Ask who owns any account that lacks a clear identity.
Avoid removing accounts solely because they have not signed in recently. A named backup may have a valid purpose. Require the owner to confirm that purpose and the right access level. Unexplained inactivity should trigger a closer check.
Include application accounts used for integrations or scheduled work. Identify the person responsible for each connection and what data it can reach. Do not disable an unfamiliar account blindly; first check its purpose and dependencies unless urgent containment requires immediate action.
Step 2: Review firm and admin roles
Check who can add users, change permissions, export records, manage payments, and alter security settings. Separate routine work from administration where the system supports it. Confirm that temporary elevated access has a reason and a review date.
The account lifecycle matters during every law firm access review. A departure process should address relevant systems when the person leaves. Periodic checks then look for omissions and later changes; they should not become the only route for removing access.
For shared accounts, identify a supported path toward individual accounts. If a shared credential must remain temporarily, document its users, purpose, safeguards, and replacement plan. A shared name makes it harder to connect an action to a person.
Step 3: Check matter access against current work
Compare each matter’s allowed users and teams with the current team plan. Check temporary cover, former team members, and cross-practice groups. Review especially sensitive files according to the firm’s approved restrictions.
Do not infer confidentiality clearance from a broad department label. Confirm membership of the group that grants access. A group called Litigation may contain people whose assignments have changed since it was created.
A law firm access review should also examine the starting settings for new matters. If the same broad permission keeps returning, revise the opening process. RunSensible’s file-opening checklist discusses setting access and confidentiality controls before work proceeds.
Step 4: Check documents and sharing routes
Inspect folders, individual files, guest access, and share links where the tools provide those controls. Check how inherited permissions work: a file may receive access settings from its parent folder. Record any exceptions created directly on the file.
Ask whether the intended recipient needs the whole folder or only one approved document. Check the recipient, allowed actions, expiry options, and whether the link can be forwarded or opened without signing in. Use the controls supported by the platform.
Include released copies in the law firm access review. A document stored correctly inside the firm may also have been emailed or copied elsewhere. Record what the review can establish and what requires follow-up. Permission changes in one location do not account for every copy.
Step 5: Verify client portal users and shared items
Confirm the person behind each portal account and the email used for invitations. Check the matters, documents, bills, forms, and requests made available to that account. Review access when a representative changes or an authorized relationship ends.
Take particular care where several people relate to one matter. A client, company officer, family member, and billing contact may need different information. Ask the responsible lawyer to approve the recipient and scope rather than assuming every associated contact can see the same material.
A law firm access review should test a portal change against the intended outcome. If one shared item needs correction, establish whether the tool supports that adjustment before disabling an account serving other legitimate matters. Document the chosen action and who authorized it.
Step 6: Review connected accounts and sessions
Ask the admin to check connected applications, direct application accounts, forwarding arrangements, and active sessions where supported. A password change or central account block may not complete every application’s revocation process.
Microsoft’s Entra guidance explains that applications can maintain their own sessions and authorization policies. It directs admins to consider removing users from applications and session behaviour when revoking access. Apply the documentation for each system your firm actually uses.
Include known exports and synced folders when they fall within scope. Ask your technical provider how managed devices and stored copies should be handled. Preserve required records and evidence; do not use a routine permissions review as permission to delete client material.
Step 7: Approve and apply changes
Use clear decisions: retain, reduce, remove, or investigate. A decision to retain should state the present need. A decision to investigate needs an owner and a target date so uncertainty does not become permanent access by default.
For each approved change, identify the exact account, resource, action, and effective time. Coordinate dependencies such as task ownership or an integration used by the team. Record failed changes and refer them promptly to the right admin or provider.
Keep temporary exceptions visible during the law firm access review. Name the approver, purpose, scope, safeguards, and expiry or next review. If a tool cannot enforce expiry automatically, assign a dated task to revisit it.
Step 8: Verify the result and close the record
Check that the intended access now works and the removed access no longer works through the routes in scope. Use an approved test account or provider-supported method. Never ask a client or colleague to share their password for testing.
Test the actual action where practical. Opening a document does not prove a download restriction works. Hiding an item from a menu does not establish that an earlier direct link is blocked. Ask the provider how to test controls that your admin cannot safely verify.
Close a law firm access review only after recording changes that passed checks, open gaps, and approved exceptions. A saved setting shows an attempted change. Your record of the checks should explain the observed result and any limits of the test.
Choose a schedule based on risk and change
Pair a scheduled law firm access review with checks triggered by events. Consider departures, role changes, contractor completion, new integrations, a changed client representative, and changes to a sensitive matter’s team. Some events call for immediate action under the firm’s process.
A practical starting schedule
A firm might check privileged and external access monthly, run a broader law firm access review quarterly, and review the policy annually. This is a suggested starting point, not a universal legal timetable. Adjust it to the volume of change and the sensitivity of the work.
The Canadian Centre for Cyber Security’s access-control catalogue includes periodic review of privileges at a frequency chosen by the organization. It also describes reassigning or removing rights when the need cannot be confirmed.
Record why the firm chose its intervals. A small practice with frequent contractors may need closer external-access checks than a stable team. A long gap between scheduled reviews should never postpone a known departure or urgent exposure.
Fit the review to confidentiality duties
In the United States, ABA Model Rule 1.6(c) addresses reasonable efforts to prevent unauthorized access or disclosure. It is a model rule; confirm the rules adopted in the relevant jurisdiction. The checklist supports a working process rather than establishing compliance by itself.
In Canada, the Office of the Privacy Commissioner explains that safeguards under PIPEDA should reflect information sensitivity and restrict access on a need-to-know basis. Its guidance also recommends regular review of safeguards. Confirm which privacy laws and professional obligations apply to your practice.

Work through a realistic permissions change
Consider a fictional family-law firm using temporary leave cover. A clerk returns from leave, an outside expert finishes their work, and one client’s approved contact changes. The admin starts a law firm access review for those affected records.
Confirm the intended access first
The responsible lawyer checks which files return to the clerk and which remain with the covering team. The expert needs no further workspace access. The lawyer separately confirms what the new client contact may receive and whether the earlier contact retains any authority.
The coordinator lists the relevant matter permissions, document shares, and portal records. They also ask whether the expert received downloaded copies. That question becomes a separate follow-up under the agreed handling and retention terms.
Verify each change in its own system
The admin updates the approved settings and records the effective time. Using authorized test methods, they confirm the new internal team can work and the expert’s former sharing route is blocked. They verify portal sharing against the lawyer’s instructions.
One external tool does not provide a clear session-revocation result. The coordinator records the gap, assigns the provider follow-up, and keeps that item open. The law firm access review can report completed changes while showing that checks remain incomplete for that route.
Best practices for keeping the process useful
Begin your law firm access review with a manageable scope, such as privileged accounts and external sharing for a small set of sensitive matters. Confirm that your register captures decisions and verified outcomes before extending the process across the firm.
Measure gaps and follow through
Track overdue removals, ownerless accounts, expired exceptions, and changes awaiting checks. Count both findings and their resolution. Avoid treating a low number of findings as proof that access is correct when the inventory is incomplete.
Use repeated findings to improve the source process. If former cover staff repeatedly retain access, add a return-from-leave task. If old links recur, update the document-sharing procedure. Connect release practices with a clear document version-control workflow.
Keep the law firm access review record itself restricted. It can reveal who administers systems and where sensitive material is stored. Apply a retention decision to these records and preserve evidence needed for incidents, disputes, or other applicable holds.
Common mistakes to avoid
Reviewing only employee accounts leaves guests, applications, and shared resources outside the picture. Build the law firm access review population from each relevant system and have someone confirm its coverage.
Approving every existing permission without a current reason preserves old decisions. Ask reviewers to connect access to an assignment or approved purpose.
Removing access before arranging cover can interrupt time-sensitive work. Coordinate the handover while following the urgency required for the particular situation.
Treating a completed checklist as a compliance certificate overstates the result. Record the scope, checks, evidence, and unresolved limits of the law firm access review.
If findings suggest unauthorized disclosure or suspicious use, move the issue into the firm’s incident-response process. Preserve relevant evidence and involve the responsible lawyer and technical lead. Assess any reporting or notice duties through the applicable process.
Frequently Asked Questions
Who should approve matter access?
Assign that decision to a lawyer with responsibility for the matter and authority under firm policy. Admins can apply settings, but they need clear instructions about the permitted people, information, and actions.
Does multifactor authentication replace an access review?
No. It helps verify sign-in. The firm still needs to decide what each signed-in account can do. Include both sign-in protection and permissions in the wider security programme.
Should closing a matter remove all client portal access?
Decide under the firm’s closure, client-service, and retention processes. A client may still need shared records. Confirm the intended continuing access and the controls your platform provides before making changes.
Can we use a spreadsheet to manage the review?
Yes, as a restricted review register. Link decisions to source records, assign follow-up, and protect the sheet itself. Verify changes in the actual systems rather than treating an edited spreadsheet as evidence that access changed.
Does revoking a link recover a downloaded document?
Do not assume it does. Establish what the platform controls and whether copies were already downloaded or sent elsewhere. Handle known copies through the applicable agreement, device process, retention policy, and incident process when needed.
What should a solo lawyer do without a second reviewer?
Document the review and use a technical provider to verify settings within an authorized scope. Keep responsibility for client confidentiality and matter decisions clear. Avoid granting broad client-file access merely to make the review easier.
Conclusion
A law firm access review should connect every retained permission to a current need and every approved change to a checked result. Start with a complete scope, involve the right decision makers, and keep open items visible until someone resolves them.
Choose one sensitive matter and trace its internal team, documents, external shares, and portal users. Use what you find to improve the firm’s account lifecycle and opening, handover, and closure processes.
Resources
Sources reviewed on November 3, 2026. The checklist, register, suggested schedule, and fictional example are editorial recommendations.
Disclaimer: The content provided on this blog is for informational purposes only and does not constitute legal, financial, or professional advice.


