/001/
Overview
Teams need to belong to organizations, switch between them, and invite members — while every task and setting stays scoped to a single organization.
My role
Full stack development: frontend, API, database model and invitation flow.
/002/
Stack
- Next.js
- NestJS
- Prisma
- PostgreSQL
- RabbitMQ
/003/
Architecture
Next.js frontend, NestJS API, PostgreSQL through Prisma, RabbitMQ for queued work; every query is scoped by organization at the service layer.
/004/
Key features
- /001/Organization switcher
- /002/Organization settings
- /003/Team member management
- /004/Invitation creation and acceptance flow
- /005/Org-scoped workflows
/005/
The hard problem
The hard problem
Invitations have to be safe to accept across sign-in sessions and can never grant access to the wrong organization.
Solution
A token-based invitation flow with organization-scoped membership checks before any access is granted.