Separate identity from institution access
Google sign-in establishes identity, while platform authority and institution membership independently determine what a person can see and do.
FormFlow
website
A bilingual, institution-configurable operations platform that keeps form definitions, immutable versions, assignments, progress, notifications, and audit history attached to one submission.
- Role
- Product design and full-stack engineering
- Scope
- Multi-tenant authorization, configurable workflows, and bilingual service delivery
- Status
- Public early-stage deployment
Problem
Institutions often manage operational requests across chat, spreadsheets, fixed forms, and verbal follow-up, separating submitted information from ownership, current status, and accountability.
Constraints
- C1
English and Bengali must be complete interfaces, with locale-aware content and Bengali or Latin numeral handling where appropriate.
- C2
Google identity, platform authority, and institution membership are separate security boundaries, so every protected read and mutation must be authorized on the server.
- C3
Historical submissions must remain interpretable after an institution edits a form or workflow, requiring immutable published versions and explicit state transitions.
- C4
Google OAuth, Neon, Resend, and Netlify depend on environment-specific configuration without moving credentials into source control.
Architecture
TanStack Start routes and server functions deliver role-aware React workspaces; framework-independent domain modules own forms, workflows, status transitions, and authorization; Drizzle repositories scope Neon PostgreSQL records by institution and actor; Better Auth, Google OAuth, Resend, Netlify Functions, and GitHub Actions form the identity, communication, deployment, and quality boundaries.
01
Role-aware interface
Locale-aware TanStack Start routes and React workspaces for platform administrators, institution managers, requesters, and employees
02
Domain rules
Framework-independent form validation, workflow versioning, ordering, permissions, assignments, and status transitions
03
Institution-scoped data
Drizzle repositories over Neon PostgreSQL with immutable form and workflow versions, notifications, work logs, and audit events
04
Identity and delivery
Better Auth with Google OAuth, Resend invitation email, Netlify SSR functions, and GitHub Actions quality gates
Decisions
Version published forms and workflows
Each submission retains the immutable Form Version and Workflow Version it entered, so later edits cannot rewrite the meaning or required process of historical work.
Enforce authorization at server and repository boundaries
Role-aware navigation improves usability, but server functions and institution-scoped queries remain the security controls for every protected read and mutation.
Separate requester updates from internal work records
Employees and managers can preserve operational detail without publishing every internal note to the person who submitted the request.
Contribution
- Designed role-specific journeys for Super Admins, Admins, Managers, Requesters, and Employees across English and Bengali interfaces.
- Built dynamic form creation, immutable publishing, configurable workflows, submission tracking, assignment, work updates, notifications, invitations, profiles, and audit views.
- Modeled tenant boundaries, delegated Manager capabilities, versioned records, and role-specific data access across domain modules, repositories, and database migrations.
- Established automated domain, application, authorization, route, and presentation checks with GitHub Actions and a Netlify SSR deployment.
Outcomes
- Institutions can define bilingual forms and operational workflows without changing application source code.
- Requesters can submit a published form, receive a tracking number, and follow requester-visible progress from one record.
- Admins and delegated Managers can review queues, assign Employees, manage people, and inspect accountable history within their institution.
- Employees can accept assigned work, record progress and evidence, and complete or return the assignment through explicit workflow states.
- Published versions, work logs, notifications, decisions, and audit events preserve a traceable history as the process evolves.
Product screenshot
Verified stack
- TanStack Start
- React 19
- TypeScript
- Tailwind CSS
- Better Auth
- Google OAuth
- PostgreSQL
- Neon
- Drizzle ORM
- Resend
- Zod
- Hugeicons
- Netlify
- GitHub Actions
- CI/CD
- System Design
Working through something similar?
Share your challenge, scope, and timeline to start a focused conversation.