MuseLegal splits the door: clients, attorneys, paralegals each get their own key

A new permissions layer reshapes the platform around a law-firm portal, where who you are decides what matters and documents you can see.

multi-tenantsecurity

MuseLegal is bolting a role-based access system onto the platform, sitting alongside the existing sharing model rather than replacing it. The new layer links people to specific matters with an explicit role - client, attorney, reviewer, or paralegal - and uses that to gate everything connected to a matter: documents, portal messages, tasks, intake submissions, downloadable files. Clients see only their own matters; reviewers and paralegals are treated as interchangeable; partners and admins bypass the check entirely.

The move is a quiet but pointed repositioning. This is no longer just a generic AI legal assistant - it's being shaped into a firm-portal product where the client experience and the internal workflow live behind different doors of the same building. The guardrails run at the database layer, not just in app code, which is the right place for them if real client data is going to flow through.

So what If you're a firm thinking about giving clients a self-serve window into their matters, MuseLegal is the fork to watch - it's the one taking the portal use case seriously.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from MuseLegal/AI-Legal-Platform, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
b0ce349f Add matter_participants-based portal access controls Griot Vault 2026-05-03 ↗ GitHub
62747299 Merge pull request #1 from MuseLegal/codex/revise-portal-permission-model-based-on-roles Griot Vault 2026-05-03 ↗ GitHub
Add many-to-many matter participant authorization model

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-98.md from inside the repo you want the changes in.

⬇ Download capture-thread-98.md