amal66 gives firm workspaces a real chain of command
The fork turns organization ownership and project roles into visible, usable controls rather than back-end plumbing.
Firm users can create an organization, see who belongs to it, assign roles, form teams, and leave or remove members. Safeguards such as keeping at least one owner are explained in the interface, while ordinary members get a genuinely read-only view.
- Organization-backed projects: choose the firm workspace when creating a project.
- Role-based working rights: managers and editors can carry out the work their role permits, without being shown controls that will fail.
- Clearer limits: sensitive actions such as deleting a project remain with the owner, and refusal messages point users toward the right person.
- Human-readable membership: names and email addresses replace opaque account identifiers.
So what Firms sharing matters across lawyers, paralegals and legal-ops staff should care because this makes collaboration governable without making every participant an owner.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?