Web application
Reference buildAtlas Portal
A client portal for a corporate business: accounts, documents, approvals and access control behind one sign-in.
- Dated
- 2025
- Product type
- Web application
- Technologies
- 4
Role
ManagerDocument workflow
- Uploaded
- In review
- Approved
Access matrix
| Cli | Man | Adm | |
|---|---|---|---|
| documents.read | allow | allow | allow |
| documents.approve | deny | allow | allow |
| reports.export | deny | allow | allow |
| users.manage | deny | deny | allow |
Working interface — not a screenshot
The short version
Why it exists.
Every build here answers a specific operational problem. This is the one it answers.
- 01
What was wrong
Client work conducted over email. Documents lived in whoever's inbox received them, approvals were a reply saying yes, and a departing employee took the thread history with them.
- 02
What we built
An account per client with its documents attached to it, approvals recorded as decisions with a name and a timestamp, and access granted by role rather than by who was on the email.
- 03
What changes
A client opens the portal and sees their own documents and the state of every approval. Nothing depends on searching an inbox, and access survives someone leaving.
What it does
The parts that matter.
Not a feature list — the four things this product is actually for.
One account per client
Everything about a client — people, documents, history — attached to the account rather than a mailbox.
Documents with a home
Versioned, attached to the work they belong to, and findable by someone who was not there.
Approvals on the record
Who approved what, when, and against which version — recorded rather than remembered.
Access by role
Permissions follow the role, so onboarding and offboarding are a change rather than a cleanup.
What it took
The disciplines behind it.
How it is built
The technologies.
Chosen because they suit the problem and because a team other than ours can maintain them.
- Next.js
- TypeScript
- PostgreSQL
- OAuth
This build has a full interactive system behind it in the showcase — the storefront, the operations side, and the connection between them.
Open the systemStart a project
You have seen what we build. Now let us build yours.
Tell us which part of the business you want to run better. We will come back with how we would approach it, what it would take, and whether we are the right people for it.
- 01An engineer reads the brief — not a sales inbox.
- 02You get a written response on approach, risk and rough shape of effort.
- 03If it looks like a fit, a call to pressure-test the scope.