Client Portal
v1.0.0
Open live demo → Screens
Overview
Two shells over one set of records. The studio works in it all day — write a proposal, send it, and watch a project appear the moment the client accepts — while the client gets a minimal centered portal, no sidebar and no view of anyone else’s work, reached with nothing but an email address and a document number, to read the scope, approve a deliverable and settle an invoice. The manifest scaffolds the client, proposal, project and invoicing tables into your connected database and generates the record-keeping around them: the portal is the front of house, the dashboard is the office.
Capabilities
- Payments
- File storage
- Email receipts
What you get
Tables it adds9
- clients
- proposals
- proposal_items
- projects
- milestones
- deliverables
- invoices
- invoice_items
- payments
Created fresh, or mapped onto your existing tables at install.
Pages your dashboard gains5
- Studio dashboardOutstanding, overdue and active projects, with an aging list and recent payments.
- ClientsA searchable directory, each client opening onto one timeline of their proposals, invoices and projects.
- ProposalsA CRUD grid with status chips, and the priced lines under each proposal.
- InvoicesEvery invoice with its lines and the payments recorded against it.
- ProjectsA board of active, paused and finished work, with milestones and deliverables on each card.
Roles it pre-builds1
- studio-ownerRead and write every client, proposal, project, deliverable and invoice; payments can be recorded and corrected but never deleted, and settings and roles stay out of reach.
Settings you configure6
- Studio name
- Invoice number prefix
- Default tax rate
- Payment terms (days)
- Currency
- Reply-to address
Deploy it
Client Portal is a static frontend. Deploy it in one click, or grab the source and host it anywhere. It runs on built-in demo data today and connects to your Adminium instance when the publishable-key API lands.