October 28, 2026
Who can access your client information, and from which devices?
An independent broker may finish working with a brokerage while a shared client folder remains available to them. A private mortgage firm…

By Refocus Technology Solutions
5 min read
- 1 Why are client data access controls a leadership issue?
- 2 How can appropriate access become excessive over time?
- 3 Why do accounts and MFA answer only part of the question?
- 4 What changes when client information reaches a personal device?
- 5 Why does employee offboarding need more than an account change?
An independent broker may finish working with a brokerage while a shared client folder remains available to them. A private mortgage firm may close an external assignment while access to borrower records continues. An employee may change roles and retain permissions that were appropriate for their previous responsibilities.
In these situations, the original access decision may have been reasonable. The exposure emerges because the business changed and the permission did not.
Direct answer: Client data access controls govern who can use sensitive client information, what they are permitted to do with it and the conditions under which access is allowed. For leadership, the important question is whether those permissions still reflect the firm's current roles, relationships and business needs.
Why are client data access controls a leadership issue?
Access to information carries authority. Someone who can read a record may learn sensitive details about a client. Someone who can alter, download or share it can affect how the business uses and controls that information. Those are different consequences, even when the people involved are trusted.
For a commercial brokerage, the information may include client financial statements, claims history and policy details shared across several relationships. For a private lender or mortgage administrator, it may include borrower identification, underwriting material and investor records. A person's involvement in one part of the work does not establish a business reason to access every related record.
The principle of least privilege gives this issue a clear foundation: permissions should reflect what a person needs to perform the authorized task. Leadership provides the business judgement behind that decision. The technology team implements the permissions that support it.
How can appropriate access become excessive over time?
Access management becomes difficult when permissions outlast the reason they were granted. A temporary assignment becomes an ongoing group membership. A colleague covers a role and keeps the additional access afterwards. An external party is known to the business, but nobody has agreed who confirms when their work has ended.
Imagine a brokerage where an independent broker needs selected commercial client files. A broader folder permission may make the immediate task easier. As the relationship evolves, that convenience can leave the brokerage unable to explain why the wider access remains appropriate.
At a private mortgage firm, an external professional may need documents for a specific development-finance assignment. Their legitimate involvement does not settle whether access to other borrower files or investor correspondence is necessary. Effective client data access controls preserve that distinction as the work changes.
The management issue is the connection between authorization and current purpose. A permission can be technically valid while its business justification has expired.
Why do accounts and MFA answer only part of the question?
Multi-factor authentication helps establish that a person has the required authentication factors when signing in. It does not determine whether that person should be able to open a particular client folder or whether the permission should have ended last month.
Shared passwords can further weaken accountability because several people act through the same identity. A properly managed shared mailbox is a different arrangement: staff can work together through delegated permissions attached to individual accounts. The executive concern is whether the firm can connect access to an authorized person and a current business purpose.
Microsoft 365 security therefore requires more than confirming that the organization has licences or that users encounter an authentication prompt. Configuration, permissions and business ownership need to support the same operating standard. A reassuring product name does not establish what the firm has actually implemented.
What changes when client information reaches a personal device?
A permitted user and a well-protected device are separate considerations. A company account can be used from a personal laptop, while downloaded records may be stored outside the environment the firm manages. Personal device security affects how much confidence leadership can place in its control over that information.
Microsoft documents options to limit access from unmanaged devices in SharePoint and OneDrive. Their availability and effect depend on configuration, supported access methods and licensing. That is why Microsoft 365 security should be evaluated against the firm's actual environment rather than assumed from a feature description.
The business consequences of personal device security are explored further in The work on your team's home devices and how to check it is protected. The central point is that removing access to a live folder should not be treated as proof that every previously downloaded copy has disappeared.
For a brokerage or lender, this creates a boundary that has to be understood. Some information may remain under the firm's technical control. Other copies may depend on an agreed external handling arrangement. Leadership needs an honest explanation of both.
Why does employee offboarding need more than an account change?
Employee offboarding connects access removal with the continuity of the work. The firm needs to end unnecessary access while preserving records and responsibilities that remain important. Separate portals, external sharing and third-party applications can complicate that handover.
Microsoft's guidance on removing a former employee and securing data treats access blocking, information preservation and handover as related activities. The specific actions depend on the environment. Leadership should therefore judge employee offboarding by the business outcome it establishes, rather than by whether one administrative action was completed.
Role changes deserve the same management attention. The person may still be an employee, but their authority to use particular information can have changed. Access management needs to follow that change in responsibility.
What would a credible answer to leadership look like?
Reliable client data access controls should give leadership a defensible picture of who has access and why. An access inventory helps make the environment visible. Named business owners establish who can authorize the use. Documented exceptions explain where the operating standard has not been met and what decision remains open.
Those records are useful only to the extent that they reflect the working environment. A report generated from one system can miss separate applications or external copies. A complete-looking list can also conceal an outdated business justification. Interpreting the evidence requires both technical knowledge and an understanding of how the firm serves clients.
This is the leadership perspective behind the technology-risk questions a CEO should ask. The aim is to understand the limits of the answer and the decisions that follow, without requiring the executive team to design the access-control architecture itself.
Bring access decisions back into line with the business
Refocus Technology Solutions helps leaders understand access exposure and coordinate the work across internal teams, managed IT and specialist cybersecurity support. The focus is a business-relevant view of permissions, devices and responsibilities, followed by accountable action.
Explore Refocus Technology Solutions cybersecurity services to discuss the access questions your financial firm cannot yet answer with confidence.
Start a technology-risk conversation with Refocus Technology Solutions
Frequently asked questions
What are client data access controls?
They are the rules and settings that govern who can use client information, which actions they can perform and the conditions of access. They should reflect current business responsibilities and the sensitivity of the records.
Does MFA establish that client information is protected?
MFA strengthens authentication. It does not by itself establish appropriate permissions, a protected device or control over downloaded copies. Those questions require separate consideration.
Who should approve access to client records?
A named business owner should determine whether access is needed for the work. The operational team and provider implement the agreed decision and coordinate changes within their responsibilities.
Does employee offboarding remove every copy of client information?
It should not be assumed to do so. The result depends on the systems, devices and external sharing involved. Previously downloaded copies may require a separate handling process.
What evidence should leadership expect?
An access inventory, named owners and documented exceptions provide a useful management view. Their scope, accuracy and review status matter as much as their existence.
Sources and publishing notes
Canadian Centre for Cyber Security. Implement access control and authorization:https://www.cyber.gc.ca/en/guidance/implement-access-control-and-authorizationMicrosoft Learn Control access from unmanaged devices: https://learn.microsoft.com/en-us/sharepoint/control-access-from-unmanaged-devicesMicrosoft Learn. Remove a former employee from Microsoft 365:https://learn.microsoft.com/en-us/microsoft-365/admin/add-users/remove-former-employee?view=o365-worldwideEditorial note: The commercial insurance brokerage and private mortgage finance scenarios are illustrative examples of technology-risk issues, not accounts of specific client engagements. They do not identify clients or imply an equivalent outcome. This article provides general technology-risk information and is not legal, privacy or compliance advice.