bgevconsultancy makes Helm-v2 private by default
This fork turns a single-tenant legal-AI product into one built for separate organisations and explicitly shared work.
bgevconsultancy has added organisation boundaries throughout the product, with access checks applied across chat, documents, projects, libraries and user activity. The team also built a substantial isolation test suite and expanded it after staging review.
- Organisation separation keeps one customer's records out of another's workspace.
- Private-by-default access limits records to their owner unless they are deliberately shared with a colleague.
- Storage and search results now follow the same project-access rules.
- A security review found concrete gaps around pending access, blocked users and document ingestion; subsequent work closes them.
The interesting part is the sequence: the team did not stop at adding tenant boundaries, but tested them, reviewed the weak spots and tightened the default permissions.
So what Legal product teams planning multi-client deployments should study this fork's security fixes and sharing model before designing their own.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?