willchen96 stops you from sharing a project with yourself

A small sharing-model fix that kills a confusing edge case: owners showing up as if they were just another invited member.

multi-tenantworkflow

In the original Mike, a project or tabular review owner could type their own email into the share list - which did nothing useful, since owners already have full access, but did make the owner appear as a separate person in the shared/people lists. willchen96 closed that gap. Now the app refuses a self-share on both sides: the interface blocks you from entering your own address before you submit, and the server rejects it too, so the rule holds no matter how the request arrives.

He also cleaned up the input itself, standardizing and de-duplicating share addresses before they're saved. That catches the adjacent mess - the same person entered twice, or with different capitalization - that a naive check would let slip through, keeping the member list honest.

So what Anyone whose team lives inside shared projects and review lists gets a cleaner, less confusing picture of who actually has access.

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
87e55d60 feat: prevent users from sharing projects and reviews with themselves willchen96 2026-05-16 ↗ 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-710.md from inside the repo you want the changes in.

⬇ Download capture-thread-710.md