04Give clients a front door
A front door, not an inbox.
Each client gets their own sign-in to see how their work is going, approve deliverables, pick up files, raise requests and pay invoices. Your internal notes stay internal. Nobody needs to email “any update?” again.
Meridian Logistics · Approvals
Homepage v2
Round 2 · sent by Neha Kulkarni
- Neha Kulkarni
Round 2 is up: tighter hero, the new fleet photos, and the quote form moved above the fold.
- Rhea Kapoor
Much better. Approving so dev can start.
What it replaces
- “Any update on this?” emails
- Feedback scattered across threads
- Shared drive links that expire
- Status calls that could have been a page
04.1 · Client portal
What clients see
Progress without a status call
Their active projects with tasks done of total and progress by stage, plus the updates your team posts. Internal projects never appear.
Files that stay put
Every file is internal or shared. Shared files appear in the portal across all of the client's projects, up to 25 MB each, checked for integrity on upload.
Invoices in one place
Issued invoices with their status and a PDF to download. Drafts are never shown.
04.2 · Client portal
Approvals and requests
Approve or ask for changes
Send a deliverable with a description and a file. The client approves it, or requests changes and has to say what. Work sent back is resubmitted as a new round, and every decision is on record.
Requests with urgency
Clients raise a request with a type, an urgency and the project it's about. You can reply in the thread, and closed requests take no more messages.
Internal notes, never shown
Deliverables and requests each have a conversation. Staff can leave internal notes on the same thread that the client never sees.
Requests
From client portals- Normal
Add the Pune office to the contact page
Change · Meridian Logistics
- Urgent
Checkout button broken on Safari
Bug · Meridian Logistics
- This week
Diwali offer banner for the homepage
New work · Meridian Logistics
Add to project plan turns a request into a task, with the client’s words as the brief.
04.3 · Client portal
Kept in the loop
Emails that go to the right people
Clients hear when work is sent for approval, when you reply, when an update is posted and when their request starts or finishes. Your project lead hears about decisions and new requests.
Invited, never signed up
Portal logins are invited per client and can be suspended at any time. A staff account can never become a portal login, or the other way round.
Separated by design
The portal runs on its own API with its own checks. Every query is filtered to the signed-in client, in the data layer, not just hidden in the UI.
Step by step
An approval round
- 1
Send
Your designer uploads Homepage v2 and sends it for approval.
- 2
Notify
Every active portal login at the client gets an email with a link.
- 3
Decide
The client approves, or requests changes with feedback.
- 4
Close the loop
Your lead is told. A request for changes is resubmitted as the next round.
The details that matter
- Clients only ever see their own organisation's work
- Internal notes are filtered on the server, not hidden with CSS
- A failed email never blocks the change that triggered it
- Suspending a login signs it out everywhere
- Installable on a phone like an app, with push notifications
Try it in the demo
Sign in as Meridian Logistics, the client.
- 1Open Approvals and decide on a deliverable
- 2Raise a request and pick an urgency
- 3Open Invoices and download a PDF