Authentication that stays out of the way

Clerk handles all the authentication for the client portal. Sign up, sign in, session management, protected routes — the whole thing. I did not build a custom auth system because building auth is how you introduce security bugs. The signup flow takes about thirty seconds. Once you are in, you see your projects, your bookings, your invoices, your deliverables. The portal knows who you are and shows you only your stuff. No shared dashboards, no magic links that expire after an hour. Just a proper auth layer that remembers you and gets out of the way. The commit history shows the auth integration going in alongside the portal features — not as an afterthought, not bolted on after launch. Authentication was part of the first portal commit because it has to be. A client portal without auth is just a public page. Clerk also syncs to the database through webhooks, so when someone signs up their profile exists in Prisma before they even finish the redirect. That means the portal can show personalised content from the first page load.