A law firm brings on four people in the same month: a lateral partner, a legal assistant, someone in finance and a contract attorney joining for a specific matter. IT follows the familiar process and provisions each person with the firm’s standard desktop. From a support and security standpoint, that consistency has traditionally made a lot of sense.
But the way those four people actually work may look very different. The partner spends much of the day in Word, Outlook, the document management system and practice-specific applications. The legal assistant moves across multiple attorney workflows and matter-based systems. The finance employee may rely on their own mix of financial systems, reporting tools and browser-based applications. The contract attorney may need controlled access to only a small portion of the firm’s applications and data, and only for a limited period of time.
Law firms have good reasons for standardizing technology, particularly when legal workflows depend on tightly configured applications, integrations and security controls. What has changed is the number of ways firms can now deliver those resources. A full Windows desktop may still be the right fit for some users, while others can work effectively through SaaS applications, selected published applications or a different combination.
So does everyone in the firm still need the same desktop? For most firms, the honest answer is that most people probably do, but not necessarily everyone. The more useful exercise is separating the controls that should apply to every user, including identity, access, endpoint protection and support, from the workspace itself, which can reasonably vary by role. That leads to the question worth asking before the next major technology decision: what truly needs to be standardized across the law firm, and what can vary based on how different groups work?
Why the standard desktop worked
For years, giving employees a consistent desktop solved a practical problem. IT could control application versions, configurations, security settings and integrations. Users had a familiar experience and support teams had fewer variations to troubleshoot.
That consistency still matters in legal work. An attorney working in Word may depend on document management integrations, comparison tools, templates, metadata controls or other add-ins tied closely to the desktop experience. Heavy Outlook use and practice-specific Windows applications can add more dependencies. Moving applications to the cloud hasn’t made those requirements disappear. Cloud applications and a consistent legal workspace are not necessarily the same thing when attorneys still rely on a mix of browser-based and desktop-dependent workflows.
There is also no reason to abandon a standard environment simply because more choices are available. If one desktop model works well across the firm, is easy to support and meets the firm’s security and workflow requirements, consistency may still be the best answer.
The case for revisiting the standard build arises when it begins producing more exceptions than consistency.
Different work may call for different workspace profiles
A workspace profile is a defined combination of applications, access and delivery method assigned to a group of users who do similar work rather than to individuals. A role-based approach starts with what those groups need to accomplish rather than assuming every user should receive the same package.
The categories will differ by law firm. An attorney doing document-heavy work may rely on advanced Word and Outlook capabilities, a document management system and several tightly configured integrations. A legal assistant or paralegal may need broad access across matters, attorneys and applications. Business-services employees can have very different requirements of their own, from Excel-heavy finance and reporting workflows to primarily browser-based HR or marketing systems. Temporary attorneys may need a narrower set of applications and matter data for a defined period.
Defining profiles is not the same as configuring every employee individually. A firm might instead identify a small number of profiles, such as a full legal desktop, a business-services environment and a limited-access workspace, then adjust them when genuine workflow requirements demand it.
Technology delivery is increasingly flexible enough to support that approach. Windows 365 can deliver complete Cloud PCs, while Windows 365 Cloud Apps give administrators a way to provide secure access to individual applications without a dedicated Cloud PC for every user. That doesn’t mean Windows 365 is the answer for every firm. It illustrates that the desktop no longer has to be treated as a single firmwide technology decision.
Different delivery doesn’t mean different standards
Giving every employee a unique setup would quickly create the opposite of what most IT teams want. Onboarding becomes harder, troubleshooting takes longer and exceptions accumulate.
Law firms have already seen how the cost of adding tools extends well beyond the software license itself. The same principle applies to workspace design. More options are only useful if they can be managed consistently.
A role-based model should therefore vary the pieces that need to vary while keeping core requirements consistent. Identity and authentication, endpoint protections, approved applications, access controls, provisioning, offboarding and support responsibility should follow firmwide standards. Client confidentiality and matter access do not become less important because one employee works through a browser while another uses a full cloud desktop.
Discipline matters here because one-off configurations rarely announce themselves. They accumulate quietly into the kind of technology debt that becomes visible only once it starts affecting productivity, governance and support.
More connected workflows make access design more important
Role distinctions become more important as applications exchange more information.
AI is one current example. Legal AI is increasingly being connected to systems firms already use rather than operating only as a standalone destination. An August 2026 expansion of the Thomson Reuters and iManage partnership is one example, bringing CoCounsel Legal, HighQ and related platforms closer to document management, with both companies describing access controls, ethical walls and privilege boundaries as carrying through to the connected workflows.
As workflows cross more systems, law firms need a clear understanding of what each role should be able to access and from where. The desktop is only one part of that design. The broader issue is making sure applications, information and permissions reflect what users need to do without giving everyone access to everything by default.
When a law firm should revisit its desktop model
Not every law firm needs to rethink its desktop model. If the current environment works well across attorneys and staff, remains manageable for IT and fits the firm’s security requirements, there may be little reason to change it. User resistance is a real constraint as well. ILTA’s 2025 Technology Survey found 57% of respondents pointing to resistance to change as the biggest hurdle to adopting new technology, which is a good reminder that workspace changes need a clear reason behind them.
The conversation becomes more useful when the firm’s operating model changes. A lateral group arrives with different application requirements. A merger introduces another set of systems. The firm relies more heavily on SaaS applications. Temporary or contract professionals need fast, controlled access. Different departments increasingly require exceptions from the standard build.
Each of those moments is a reasonable point to ask whether the current desktop model still reflects the way people work or whether the firm is maintaining uniformity simply because uniformity used to be easier.
Start with the work, then choose the workspace
Before the next desktop refresh, cloud migration, merger or major hiring initiative, identify a handful of user profiles and ask:
- What work does this group perform most often?
- Which applications, integrations and add-ins are essential?
- Which tasks genuinely require a full Windows desktop?
- What client, matter and firm data does the role need?
- Where will users work and from what devices?
- Is access permanent, temporary or tied to a specific matter?
- What can IT consistently support without creating more exceptions?
Cost belongs in the discussion, but after the requirements are clear. Giving a light user more computing environment than necessary can waste money. Giving a document-heavy attorney a less expensive setup that creates daily friction can cost considerably more in lost time and support effort.
The goal isn’t to replace one standard desktop with dozens of custom ones. It is to standardize the controls that protect the firm and make its technology manageable, then determine where different groups need different ways to access their work.
A useful starting point is to map the workflows, applications, access requirements and support needs behind a few common user groups and compare them with what the firm provides today. The lateral partner and the contract attorney who started the same month may both end up well served by the standard build. The exercise may also show where they should not be.
If your firm is evaluating whether its current desktop approach still fits the way attorneys and staff work, Afinety can work with your team to assess the applications, workflows and user requirements behind it before the next major technology decision.