# Build a client portal your clients will actually log in to

> Describe your client work and get a working client portal: a login per client, project status, shared files, comments and approvals, on a live URL you own.

Canonical: https://vibely.sh/use-cases/client-portal
Last updated: 2026-11-19

Client work leaks across tools. The latest file is in one email, the approval is in another, and the status lives in your head until the client asks for it. A client portal fixes that with four things: a login per client, the projects that belong to them, the files and updates for each one, and a clear place to approve. Vibely builds all four from a description, on a Postgres database with authentication via Supabase, and deploys it to a URL you can send to your first client the same day.

| Platform | Category | Stack | Plans |
| --- | --- | --- | --- |
| Web app | Internal tools | React, TypeScript, Supabase | [Free to start; custom domains from Pro](https://vibely.sh/pricing) |

- Included in the first build: Postgres, auth and file storage on your own Supabase project
- Yours to keep: Row-level rules so each client sees only their own work
- Deploys to a live URL — nothing for your team to install
- React and TypeScript you own, synced to your own GitHub repository
- Add a stage, a field or a new view by asking
- Free plan, no credit card, unlimited projects

## Who this is for

This is for consultants, agencies, accountants, designers and studios with somewhere between a handful and a few hundred clients, who are tired of explaining where the latest version is. If you need contracts, e-signatures and invoicing in one suite, a dedicated product will cover more ground — the case here is a portal that matches how you deliver, under your own brand.

## Start with this prompt

Paste it in and edit the details to match your own. Being specific about the screens and the data is what separates a working app from a mockup.

```text
Build a client portal for a small design studio.

Screens: a sign-in page; a client dashboard listing their projects with a status badge (In progress, Waiting on you, Done); a project page with a timeline of updates, a file list with upload and download, and an Approve button for the current deliverable; and an admin area where the studio sees every client and project.

Data: clients, projects, updates, files and approvals in Supabase, with files in Supabase Storage. Each client only sees their own projects. Studio staff see everything.

Add two example clients with a few projects each so I can see it working.
```

## What the build actually consists of

### One view per client

A dashboard listing that client’s projects and their status, a project page with updates in date order, a file area, and an approval button where you need a yes before you continue.

### Access that is actually scoped

Postgres and authentication on Supabase, with row-level rules so each client only ever sees their own projects and files, while your team sees everything. Files live in your own Supabase project.

### Your brand, your URL

Your colours, your logo and your wording, deployed to a live URL on the first build. Connect a custom domain on Pro and up so clients see your name, not ours.

Built on: [The Supabase backend](https://vibely.sh/features/database), [One-click publishing](https://vibely.sh/features/publishing), [Code you own](https://vibely.sh/features/code), [Payments with Stripe](https://vibely.sh/features/database#payments), [Custom domains](https://vibely.sh/features/publishing#custom-domains), [Row-level security checks](https://vibely.sh/features/security)

## What you get

- A sign-in for each client, scoped to their own projects
- Project pages with status, updates and a file area
- An approval step with a record of who approved what, and when
- An admin view for your team across every client
- A live URL, plus a GitHub repository you control

## What to build next

Once the first build lands, these are the prompts people send next.

1. Email the client when a project moves to Waiting on you.
2. Add a comments thread under each update.
3. Add an archive view for finished projects.

## Connectors this build uses

[Supabase](https://vibely.sh/connectors/supabase), [Stripe](https://vibely.sh/connectors/stripe), [GitHub](https://vibely.sh/connectors/github)

## FAQ

### Can each client only see their own files?

Yes. Ask for row-level security scoped to the client, and the rules are written into your Supabase database, not just hidden in the interface. They are in your code, so you can read them and tighten them.

### Can I use my own domain?

Every build deploys to a live URL straight away. Custom domains start on the Pro plan, so clients can sign in at an address with your name on it.

### Can it send emails to clients?

Yes. Connect Gmail and the app can send email from your own Gmail account, or the agent can call an email provider you choose with its API key, written in your own code. Ask for either in the prompt.

### Can clients pay invoices in the portal?

You can add payments with the Stripe connector — for example a pay-now button on an invoice. Describe how you bill and the agent wires the checkout into the portal.

## Related

- [A CRM that matches how you actually sell](https://vibely.sh/use-cases/crm) - Contacts, pipeline stages and notes shaped around your process instead of a vendor’s — with real auth and a database behind it.
- [The internal tool your team keeps asking for](https://vibely.sh/use-cases/internal-tools) - Dashboards, admin panels and workflow apps with a real database, roles and a live URL — instead of another shared spreadsheet.
- [An invoicing app](https://vibely.sh/use-cases/invoice-app) - Clients, invoices, line items and paid or overdue status — with a Stripe pay button if you want one.
- [See every use case](https://vibely.sh/use-cases)
- [Browse app templates](https://vibely.sh/templates)
