Law firms manage user roles across offices by matching access to each person's responsibilities, then applying matter-specific permissions where client work requires tighter boundaries. A shared role framework keeps equivalent jobs consistent, while documented approvals and regular reviews help the firm adjust access when someone joins, changes responsibilities or leaves.
In This Article
What should a law firm's user roles be based on?

“John brought the right knowledge to my issue and resolved it in about a reasonable amount of time. I walked away confident the problem was actually fixed.”
Start with the work people perform, not the office where they sit. An attorney, paralegal, billing specialist and firm administrator may need different access even when they share a location. A role should describe the work-related access a person needs; matter-level permissions can address narrower client or case requirements.
Build a role catalog from actual duties. It might include attorneys by practice group where useful, legal assistants, records staff, finance, intake, firm administration, IT administrators and temporary personnel. Keep roles broad enough to maintain, but specific enough to guide approvals. Creating a separate role for every individual makes the catalog harder to understand and review.
For each role, document which systems and information it can reach, who approves the access and any relevant limits. Consider email and calendars, document management, matter workspaces, practice-management and billing systems, e-discovery, client portals, remote access and shared resources. A role is useful only when its meaning is clear to the people who request and approve it.
Separate routine access from administrative privileges. A person who manages accounts or security settings should use a distinct administrative identity where the system supports it, rather than relying on broad privileges for ordinary email and document work. Record the purpose and approval for elevated access, and make clear who is responsible for reviewing it.
Three lifecycle checkpoints: joining, changing responsibilities and leaving.
- Joining: confirm the person's role, systems and any matter-specific access.
- Changing responsibilities: add access required for the new work and remove access that no longer fits.
- Leaving: coordinate account and session handling under the firm's process.
These checkpoints organize access decisions; they do not replace a review of the firm's applications or client requirements. The role catalog should reflect how the firm works today and change as practice groups, workflows and systems evolve. Treat it as an operating standard that people can use, not a one-time spreadsheet.
Takeaway: define access by job responsibilities, and make exceptions visible and owned.
How should access differ by office and matter?
Office location can affect practical access needs, but it should not automatically determine access to client information. Someone may work in one office and support matters led from another. Being in the same building as a matter team does not, by itself, establish a need to access every file.
Use office attributes for location-specific resources such as printers, local collaboration spaces or office operations systems when appropriate. Use role and matter permissions to set boundaries around confidential work. This separation helps the firm move an employee between offices without unintentionally changing access to client matters or leaving location-specific privileges in place.
For each matter, identify who is authorized to work on it and which application enforces that decision. The relevant control may be in a document-management system, matter workspace, client portal or another application. Map the actual permission points instead of assuming that a central directory setting controls every system.
Pay attention to shared mailboxes, folders and groups. They can support legitimate workflows, but each should have a clear purpose and an owner who can confirm membership. An office or practice-area group should not quietly become a general route to restricted matter materials. Make the group's scope understandable to the person granting access.
Cross-office work also depends on consistent identity records. Maintain a reliable connection between each account, the person using it, their role and their employment status. If an attorney supports multiple practice groups or offices, document why additional access is needed and who approved it. That gives reviewers a clear reason to assess later.
Takeaway: use office context for local operations and matter permissions for client-work boundaries.
How do onboarding, role changes and departures stay consistent?
Make access part of a controlled employee lifecycle. Before a new hire starts, the manager or designated business owner confirms the person's role, office, start date, systems needed and any matter-specific access. Technology staff then provision the approved access, while the request record identifies who authorized it. A standard checklist reduces last-minute improvisation without assuming every employee needs the same setup.
When someone changes practice group, takes on administrative duties or moves offices, treat it as a fresh access decision. Add permissions that match the new work, but also remove access that no longer fits. Simply adding a new role can leave someone with privileges accumulated across years of changing responsibilities.
Coordinate departures among the firm's responsible business functions and technology support. Establish who communicates the effective date, who approves any continuity arrangements and who confirms that accounts and sessions are handled under the firm's process. Preserve or transfer work materials according to the firm's records and matter-handling procedures rather than leaving access active as a convenient workaround.
Provide a documented exception path for urgent needs, such as a lateral hire joining an active matter or a temporary specialist supporting a defined task. Record the scope, approver, start point and planned end or review point. Give a person responsibility for confirming that temporary access remains necessary; do not rely on someone remembering it later.
Keep evidence somewhere the firm can retrieve it. Useful records include the request, approver, role assigned, systems changed, exception rationale and completion confirmation. These details support internal reviews and help the firm explain its process when a client asks how access is managed. Keep the record concise enough for staff to maintain during routine work.
Takeaway: treat every change in employment or responsibility as a reason to reassess access, not just add it.
How can firms review permissions without slowing legal work?
Set a review schedule that reflects the firm's systems, obligations and ability to act on findings. Trigger additional checks after significant changes to a person's role or a matter. Assign a business owner to each role, group and sensitive workspace so that someone can make a practical decision when a review is due.
Make reviews specific. Ask owners whether each person still needs the access, whether the role remains accurate, whether shared groups still serve their stated purpose and whether exceptions have a current business reason. A report that is too broad or difficult to interpret can become a checkbox exercise. Give reviewers clear decisions they can make.
Test the process against realistic situations: an attorney changes practice groups, a paralegal joins a restricted matter, a departing employee has active sessions, or a cross-office administrator needs local resources. Trace each request from approval to the application where access is enforced. Note manual handoffs and systems whose permissions are managed separately.
Clear ownership matters because a law firm may use firm-managed accounts alongside specialized legal applications and outside vendors. Identify who approves business access, who changes each system and who follows up when a vendor must make a change. GDS Technology provides IT support and managed technology services for businesses; support for a specific system or process should be scoped to the firm's environment and agreed work.
Madhav Naik, a professional-services client, described the value of clear follow-up: "John brought the right knowledge to my issue and resolved it in about a reasonable amount of time. I walked away confident the problem was actually fixed." This is an example of issue resolution, not a claim about law-firm access management. The same practical discipline applies to access work: record what changed and what follow-up remains.
Firms evaluating outside support can review GDS Technology's IT services for law firms and how technology support relates to day-to-day legal work. For broader access and security planning, see cybersecurity services and IT help desk support. Confirm responsibilities and scope before making permission changes.
Takeaway: keep reviews focused, assign decisions to business owners and trace changes through the systems that enforce them.
Frequently Asked Questions
Should law firms use the same access roles in every office?
Use a common role framework across offices so equivalent jobs begin with consistent access. Then add documented local or matter-specific permissions when the work requires them. A shared baseline improves clarity, while scoped exceptions preserve operational flexibility. Review exceptions with an owner so they do not become permanent access simply because a person changed offices.
How should a firm handle access when an attorney changes practice groups?
Have the responsible manager confirm the attorney's new responsibilities and required systems, then review existing permissions before granting additional access. Remove privileges that no longer fit, and separately confirm access to active matters. Record the approver and changes. This avoids accumulating old and new permissions without a clear reason or owner.
Who should approve access to a client matter?
The firm should designate a business owner with authority to confirm who needs access for the matter, following the firm's own policies and client requirements. Technology staff can implement the approved change and document it, but should not infer legal-work eligibility from office location or job title alone. Make the approval traceable.
How often should law firms review user permissions?
Set a review schedule based on the firm's applications, risk, client requirements and ability to act on findings. Also trigger reviews after departures, role changes and significant matter changes. The schedule is useful only if a named owner can decide whether access remains appropriate and ensure changes reach each relevant system.
Follow GDS Technology on Facebook, and subscribe on YouTube for new videos.