Role-Based Permissions for Law Firms: What a Paralegal Should See That a Receptionist Should Not

I have sat in on enough onboarding calls with law firms moving to Casely that I can usually tell within the first ten minutes, before we have even gotten to trust accounting or conflict checks, which firms have actually thought through who on their team should see what, and which firms have just never asked the question, right, because everyone who works there has been there for years and is trusted, so the login just says "staff," and staff means everyone can open everything. And that is basically the exact setup that gets a firm in trouble, not because anyone did anything malicious, but because a receptionist who is answering phones and confirming hearing dates ends up three clicks deep into a matter's privileged notes or its trust ledger balance, because nothing in the software drew a line and said this part is not for you. Let me be very honest, this is one of the most common gaps I see in firms that migrate off spreadsheets or off a generic CRM, and it is also one of the fastest things to fix once you actually sit down and map roles to what they need, so that is what this post is about.

The scenario that actually happens

Here is the version of this I hear most often. A client calls the front desk asking to reschedule a hearing, the receptionist pulls up the matter to find the date, and the matter page in a lot of case management tools is just one long scroll, notes at the top, trust activity in the middle, billing history further down, documents attached to all of it. The receptionist was never trying to look at anything she should not, she was trying to do her job, and the software just handed her everything because nobody ever told the software there was a difference. Now compare that to a paralegal working the same matter, who genuinely needs to see the notes because she is drafting the next filing, needs to see the documents because she is assembling an exhibit list, needs to see tasks because she has three of them assigned to her on this file, but probably does not need to see what the firm billed the client last quarter or whether the trust account is running low, because that is a billing and partner conversation, not a paralegal one. So you have got two roles on the exact same matter with genuinely different jobs to do, and the access each of them needs looks almost nothing alike, does that make sense.

What a receptionist should actually have

A receptionist's job is scheduling, intake, and being the first voice a client or opposing counsel hears, and the permission set should basically mirror that and nothing more. She needs the calendar because she is booking and confirming hearings. She needs contacts and leads because she is the one entering a new caller's information before anyone else touches the file. She needs enough of the matter view to confirm a case exists and pull a status, open, pending, closed, and so on. What she does not need is the trust ledger, because a receptionist has no reason to see how much of a client's retainer is left, that is a bookkeeping and attorney function. She does not need billing, because invoice amounts and payment history are not front desk information. She does not need documents beyond maybe what is client facing, and for instance she almost certainly does not need reports, settings, or the users page, since none of that touches what she was hired to do.

What a paralegal actually needs

A paralegal is doing real substantive work on a matter, so the access has to widen out quite a bit compared to the front desk, but it still is not partner level access, and that distinction matters just as much as the receptionist one does. A paralegal on Casely typically needs full read and usually edit access to notes, documents, and tasks on the matters she is staffed on, because that is the actual work, drafting, organizing exhibits, tracking deadlines. She usually needs to see trust activity on her assigned matters, at least in view mode, because she is often the one fielding a client's question about their retainer balance before looping in the attorney. What she typically should not have is edit access to the trust ledger itself, since recording a disbursement or approving a wire is an attorney or bookkeeper level action given how tightly bar rules regulate that account, and she should not have access to the firm's settings, user management, or the invoice numbering and templates, since none of that is her lane either.

The line between helpful and liability

The place this actually gets serious is ethical walls, which is a different problem from ordinary role permissions, right, because a wall is not about job function, it is about a specific matter where a specific person at the firm cannot be involved at all, maybe because they came from opposing counsel's old firm, maybe because of a conflict that turned up when the name was typed into intake. Casely runs conflict checks automatically the second a name is entered anywhere in the system, against the entire firm's contact and matter history, not as a manual search someone has to remember to run, and when a wall does get set on a matter, that person is blocked from it completely, not just the notes or just the billing, the whole matter disappears from what they can touch.

Why the enforcement has to live on the server, not the screen

This is the part I try to get every firm to understand before they sign, because it is the difference between a permission system that looks right in a demo and one that actually holds up when someone tries to get around it, intentionally or not. A lot of software, and I mean a lot, handles roles by just not rendering the button or the tab for a given user, which feels fine until someone opens the browser's developer tools or just calls the same endpoint the button would have called, and the data comes right back because nothing on the server side ever checked whether that person was allowed to ask for it. The catch here is that a firm usually only discovers this the hard way, during an audit or a malpractice review, long after the software was sold to them as secure. Casely checks every request against the role and the wall status at the database and API layer, so a receptionist's account cannot pull trust ledger data even by hitting the raw request directly, and a walled off paralegal cannot pull a matter's notes even if she knows the matter ID by heart, and that also means sensitive fields like notes, matters, trust entries, and documents sit behind app layer encryption per firm, so it is not just a permission check, it is the underlying data itself that is locked down.

Getting it set up without a support ticket

The actual setup is not the hard part, and I say that having walked a lot of firms through it. Every firm using Casely gets standard roles out of the box, partner, associate, paralegal, receptionist, and an admin on the firm's side can adjust exactly what each of those roles touches across all thirteen functional areas, documents, trust ledger, billing, matters, contacts, leads, calendar, tasks, settings, users, reports, conflict checks, portal access, and audit logs, without opening a support ticket or waiting on us to make the change for them. Two factor authentication sits on top of all of this as its own layer, and once a firm turns it on it is enforced, not optional, no bypass, no remember this device loophole, and an admin can check who on the team has actually enrolled from the Users page, which for instance matters a lot the week after you roll it out, when you want to know who still has not scanned the QR code yet.

At the end of the day this is maybe twenty minutes of work the first time you do it, and firms who do it up front almost never think about it again, because the roles just quietly do their job in the background from then on, right up until the day someone tries to look at something they should not and simply cannot, which is exactly the point.

The stakes for the person actually running the firm

If you are the managing partner or the attorney whose name is on the door, the honest reason this matters is not really about software elegance, it is about what happens the day a client asks who at your firm has seen their file, or a bar complaint asks you to prove who had access to a privileged document and when, and "everyone had a login" is not an answer anyone wants to give under oath. A receptionist who cannot open the trust ledger cannot accidentally discuss a balance she misread. A paralegal who cannot touch firm settings cannot accidentally change an invoice template mid quarter. A walled off associate cannot brush up against a conflicted matter even by accident, because the wall is enforced where it actually counts, not just on the screen in front of them. None of this shows up as a line item anyone gets excited about, it is not a feature you demo with a flourish, but it is the kind of thing that sits quietly under every other part of the practice and either holds or does not when it is actually tested, and so yeah, that is basically the whole case for it.