MuseLegal locks down who can see which matter
The fork adds real access control to a platform that previously had none enforced at the data layer.
MuseLegal built a permission layer that decides, for every matter, who is allowed to look at it. Each person is assigned a role - client, attorney, reviewer, or paralegal - and the rules follow from there: clients see only their own matters, attorneys see the ones they're staffed on, reviewers and paralegals can see either, and partners and admins see everything.
The key move is where this lives. The checks sit in the database itself, so the protection applies to matters, documents, client messages, tasks, intake submissions, and downloadable files no matter which part of the app does the asking. The same rules are mirrored in the application code, and they fail closed - when something goes wrong, access is denied rather than granted. No tests shipped with it yet.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?