When a personal injury legal assistant changes roles, the firm should review every assigned Clio Manage role, relevant matter and group access, and billing or reporting visibility. Define the new permitted work first. An authorized administrator should approve and verify the resulting changes.
Why does a role change need an access review?
A continuing employee may move from general case administration into a narrower records-follow-up assignment. The new title does not describe every action the account can still perform. Start with the new approved tasks and the access they require. This article concerns an internal role change, not employee departure or caseload reassignment.
For a personal injury practice, the administrator might need to distinguish access to assigned matter documents from permission to view financial records or run reports. Use a written request from the responsible firm manager. Do not ask the assistant to decide which confidential material the new role should include.
Does adding a restrictive role cancel an older role?
No. Clio documents that multiple assigned roles inherit the most permissive permissions. Standard-role permissions that cannot be configured also carry into custom roles based on those templates. Custom roles are available on selected plans. Check the current account and documentation before choosing a configuration.
An administrative review should list each current role beside the intended task. Mark a role for retention, removal or clarification, with the approver named. The list is a decision aid. It is not permission for the assistant to remove a role, create an administrator account or borrow another person's login.
Is matter visibility the same as financial visibility?
No. Clio's matter documentation describes user and group visibility controls separately. It also warns that billing or accounts permissions may allow access to a restricted matter's bills, and reports permissions may reveal matter details. These documented matter controls apply to Clio Manage, not Clio Grow.
Record both the intended matter access and the intended financial or reporting access. A successful check in one screen is not a complete review of the other. Where the new task does not explain a permission, ask the designated firm owner to decide it before the administrator changes anything.
What should an approved role-change record contain?
| Record element | Question the firm must answer |
|---|---|
| Approved work | Which specific administrative tasks continue, start or stop? |
| Current access inventory | Which roles, groups and relevant matter grants are currently assigned? |
| Desired access | What should the worker be able to view or do after the change? |
| Approved changes | Who authorized each change, and who will apply it? |
| Verification | Which permitted and denied actions will be checked using synthetic data? |
| Unresolved exceptions | Who decides them, and what restriction applies while they remain open? |
Keep the record in an approved internal location. Refer to matters through the firm's permitted internal identifiers rather than copying client facts into an external ticket. The assistant may prepare the inventory from information they are authorized to see. The reviewer should not grant wider access merely to make inventory collection easier.
Why should bulk changes receive a separate check?
Clio states that bulk matter-permission edits replace the existing selections. A user who should retain access must be included in the new selection. That is a reason to review the proposed change carefully, not a recommendation to make a bulk change.
Before any approved batch operation, the administrator should confirm its scope, the intended access after the change, and how an error would be corrected. If the firm cannot establish those points, keep the change pending. A support worker should not experiment on live matters to discover what a bulk action does.
How can the firm verify the result without using client facts?
Use a firm-approved test arrangement with synthetic records. Write down expected results before checking them. For example, an account with the intended permissions may need to open a fictional assigned matter while being unable to perform a financial action outside the role. The administrator chooses a supported test method for the account; this article does not assume a particular impersonation or test-account feature.
Synthetic example: a worker changes from billing support to document follow-up. The administrator reviews the old financial role alongside the continuing matter access, approves a change, and checks the expected allowed and denied actions. No actual person, client file or completed implementation is described here. If a result differs from the approved expectation, record the exception and return it to the administrator.
Who owns confidentiality and legal decisions?
The firm owns its access policy and supervision. An assistant may collect approved evidence, compare it with the written request and report a mismatch. The assistant does not decide conflicts, client disclosure requirements or what the law permits. ABA Model Rule 5.3 describes responsibilities concerning nonlawyer assistance; counsel confirms the applicable jurisdictional rules. Product settings alone do not establish compliance. This article is operational information, not legal advice.
The separate staff-departure handoff guide addresses case continuity when someone leaves. For administrative help maintaining the firm's approved systems, see legal software and CRM administration support. Remote Legal Team LLC can discuss support scope without taking over the firm's approval authority.
Frequently asked questions
Does a more restrictive Clio role remove an existing broader role?
No. Clio says multiple assigned roles inherit the most permissive permissions. Review all assigned roles; adding a restrictive role alone does not cancel a broader grant.
Can restricted matter information still appear in bills or reports?
Clio warns that billing or accounts permissions can expose a restricted matter's bills, and reports permissions can expose matter details. Review these access layers separately.
Can every Clio account use custom roles?
Clio documents custom roles for selected plans. Confirm the current plan and administrator options instead of assuming the feature is available.
Should a legal assistant approve their own access changes?
No. The assistant can prepare an authorized inventory and document questions. The firm-designated approver and administrator decide, apply and verify access changes.
Sources
- Clio: Roles and Permissions in Clio Manage. Updated July 30, 2026; checked October 3, 2026.
- Clio: Matter Permissions and Rates. Updated August 25, 2026; checked October 3, 2026.
- ABA Model Rule 5.3: Responsibilities Regarding Nonlawyer Assistance. Official model-rule text checked October 3, 2026. No universal compliance claim.
