// the take
A Laravel package (6+) that bolts a User-to-Team many-to-many relationship, a current-team concept, and an email-invite workflow onto an existing Eloquent User model via traits. It's aimed at developers building multi-tenant or team-based SaaS apps who don't want to hand-roll the pivot tables and invite logic themselves.
Implemented as traits (UserHasTeams, UsedByTeams) rather than forcing inheritance, so it drops into an existing User model without restructuring your app. It fires real domain events (UserJoinedTeam, UserLeftTeam, UserInvitedToTeam) so you can hook billing or notification logic in without touching package internals. The UsedByTeams trait auto-scoping queries to team_id removes a very common source of copy-pasted WHERE clauses. It has an actual test suite running in CI (GitHub Actions), not just a badge for show.
Authorization is binary — owner vs. member, via the TeamOwner middleware — so any app needing roles like admin/editor/viewer has to build a whole permissions layer on top. The current_team_id model means a user is 'in' one team at a time; apps that need concurrent per-request team context (e.g. an API serving multiple orgs) will have to work around that design rather than with it. The invite accept/deny tokens have no visible expiration logic, so a leaked invite link is valid forever unless your own code adds a check. The make:teamwork scaffolding only generates Blade views and web routes, so API-only or SPA-driven apps get effectively nothing reusable from it and have to write their own controllers and endpoints anyway.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →