amal66 brings chats into the permissions fold
This makes shared legal work easier to find and harder to access by mistake.
Chats now follow the same access rules as projects and tabular reviews, rather than operating as a separate exception. A chat shared through a project appears in the collaborator's overview as well as opening when they follow a link, closing a frustrating visibility gap.
- Standalone chats stay private unless their owner explicitly shares one with a named person.
- Editors can rename shared chat content, while viewers cannot.
- Project owners can manage chats in their own project, including chats created by collaborators.
- Review-linked chats now confirm both the review connection and the reader's permission before allowing access.
The change also replaces misleading success responses for unauthorised edits with clear denials, which matters when teams rely on shared workspaces for sensitive matters.
So what Legal teams using shared matters should care because chat history is becoming a governed part of the workspace, not a private side channel with inconsistent rules.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?