Client portal
Client sign-in requires two-factor authentication. Each client can upload, review, download, and remove their own source documents.
Software consulting by Doug Morgen
Tax document portal · Built by Doug Morgen
I built a portal for a tax practice to collect source documents and deliver completed returns. Clients sign in, upload records by tax year and document type, and return to view or download their finished documents. The preparer reviews submissions and publishes the return package from a separate admin area.
Client sign-in requires two-factor authentication. Each client can upload, review, download, and remove their own source documents.
A separate, password-protected admin area lets the preparer review client files and upload completed returns, signature pages, and other finished documents for a specific client and tax year.
Completed documents appear in the right client's portal for viewing or download. The application checks account ownership before retrieving a file; document bytes stay in private object storage rather than public site assets.
I kept document access behind authenticated routes, scoped client queries to the signed-in account, and stored files under opaque keys in a private S3-compatible bucket. Views and downloads pass through the server with private, non-cacheable responses.
Let’s talk about what you need.
Discuss a project →