- Before
- Documents and requests scattered across email threads and shared folders.
- After
- One secure portal with company sign-in and a record of who saw what.
A product catalog plus a controlled document library:
outside manufacturing partners browse products, open the files they need for
regulatory work, engineering and support, and download them from one secure place.
When something is missing, they submit a tracked request with a
named owner and a visible history, more like a service desk than a lost email.
Staff manage catalogs, files and who may see what in one system,
not across inboxes and informal folders.
How we solved it
The problem: Questions and file hand-offs lived in long
email threads and informal shared folders. It was hard to see
who asked for what, which document version was official,
and who was allowed to open it. Almost every permission change meant a
separate IT ticket.
What we built: A single web application with
two sign-in doors: internal staff sign in
with Microsoft Azure AD; users at partner organizations sign
in with Okta. Inside: a browsable catalog of products and
technologies, each linked to its documents; a
central file library in the cloud with version history and
simple uploads; and a request queue sorted by topic, where
every item has a responsible person and optional observers so the
conversation stays in one place. Access follows role rules
down to individual files. Administrators manage people, catalog content and
handovers from one place. Implementation: Next.js, PostgreSQL, AWS
(including Kubernetes for the live system), with automated build and release
through GitLab.
Screenshots change every few seconds. Hover to pause.
Built with Next.js · React · TypeScript · PostgreSQL · AWS S3 / EKS · Docker ·
Prisma ORM · NextAuth.js