amal66 makes Mike fit a law firm, not just a lawyer
This fork adds firm-level workspaces and clearer permissions without disrupting lawyers who use Mike on their own.
Each account gets a personal workspace, preserving the existing individual experience. Firms can then create shared organisations, add colleagues and group them into teams, with projects, documents, workflows and reviews kept inside that boundary.
Access is deliberately tiered:
- Owners retain the sole right to delete a project or review.
- Firm owners and admins can manage sharing, project settings and workspace structure.
- Invited collaborators can work on content without changing its structure.
- Ordinary firm members can view shared work without gaining editing or destructive rights.
The fork also applies these rules consistently across lists and individual matters, so a colleague should not see conflicting access decisions in different parts of the product.
So what Managing partners and legal-ops teams should care if they want shared matter workspaces without turning every colleague into a co-owner.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?