open-legal-products makes project sharing reliable across email variations

A small access-control repair stops legitimate project collaborators being locked out because their email address was entered with different casing or stray spaces.

securityworkflow

The Mike team has made project sharing treat email addresses consistently wherever access is checked, from a project page to project collections, searches, exports and audit views.

It also cleans up older sharing records by trimming addresses, converting them to a common form and removing empty or duplicate entries. That means a lawyer invited as Name@Firm.com should not lose access when they later sign in using a lower-case address.

The change was tested against mixed-case, padded and duplicate addresses, including a repeat run to ensure the cleanup does not keep altering records.

So what Teams sharing matters across a legal organisation should care because access now depends on the person invited, not the typography of their email address.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from open-legal-products/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
5140365c fix: normalize project sharing emails willchen96 2026-08-14 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1292.md from inside the repo you want the changes in.

⬇ Download capture-thread-1292.md