Skip to content

Guides

How to Build a Client Portal Without Code: Step by Step

Learn how to build a client portal without code: plan the pages, describe it to an AI builder, test client access and publish on your own domain.

On this page
  1. What a client portal includes
  2. Plan your portal before you build it
    1. Decide who logs in
    2. Sketch the pages on paper
    3. Decide what clients can and cannot edit
  3. Step 1: Describe the portal in plain language
  4. Step 2: Add login, client files and per-client pages
    1. Require login before any client page is visible
    2. Set up separate views for admin and clients
    3. Use attached files instead of placeholder text
  5. Step 3: Test the portal and restore earlier versions
    1. Log in as a test client
    2. Use version history to undo mistakes
    3. Test on a phone as well as a laptop
  6. Publish the portal and use your own domain
    1. Publish with one click
    2. Connect a custom domain
    3. Send each client their login and a short guide
  7. Build it with FromScratch
  8. Related builds
  9. FAQ
Illustration of how to build a client portal without code, showing a login screen and a project status dashboard on a laptop

A client portal is a private login area where each client sees their own project status, files and messages. You can build one without code by describing what you need in plain language, then testing and refining the result. This guide walks through planning the portal, describing it to an AI app builder, testing it with a fake client account, and publishing it on your own domain.

What a client portal includes

A client portal gives each client a private view of their own work. Instead of emailing status updates and file attachments back and forth, you give them one address where they log in and find everything in one place.

Most small-business portals include four things:

  • Project status: a simple view of where each job stands, such as "in review" or "waiting for feedback."
  • Shared files: the documents you send to the client, such as proposals, drafts or invoices.
  • Client uploads: a place where the client can send you assets, signed forms or spreadsheets.
  • A way to contact you: a message form or a contact page.

You do not need a server, a hosting setup or a database designed by hand. The app builder handles the front-end pages, the back-end logic and the data storage. Your job is to decide who the users are and what each one should see.

Plan your portal before you build it

Ten minutes of planning saves a lot of revision later. Start with the people who will use the portal.

Decide who logs in

Most portals have two user types:

  • Admin: you or your team, who update statuses, upload files and read client messages.
  • Client: each customer, who sees only their own information.

Write these down. The most important rule in any client portal is that a client never sees another client's data. Keep that rule at the top of your list.

Sketch the pages on paper

List the three to five screens a client needs. A typical set is:

  1. Home: current project status and any action needed from the client.
  2. Files: documents you have shared, with upload dates.
  3. Uploads: a form for the client to send files back.
  4. Contact: a simple message form.

A rough sketch on paper is enough. You are deciding what goes on each screen, not designing the visuals.

Decide what clients can and cannot edit

Split your information into two groups:

  • Changes often: status, new files, latest messages. The admin updates these.
  • Stays fixed: client name, contract terms, price. These change rarely and should be read-only for clients.

Writing this down before you build keeps the portal from becoming a messy shared document. It also gives your prompt a clear structure.

Step 1: Describe the portal in plain language

FromScratch works from a chat. You describe the app, and an AI agent builds it: a React front-end, a Python (FastAPI) back-end and a database. You do not write any of that yourself.

Be specific. Name the users, the pages and the actions. For example, instead of "a client area," write "a files page where each client sees the documents I upload for their project, with the upload date next to each file."

Give one concrete example per page. The more detail you give in the first message, the fewer rounds of correction you need.

Once the agent finishes, you get a live preview within minutes. Look at it and note what is missing. Common gaps are a missing admin view, no login screen or a files page with no dates.

Step 2: Add login, client files and per-client pages

This is the step that turns a set of pages into a portal. Three things matter here.

Require login before any client page is visible

Ask the builder to block all client pages until the user signs in. Check in the preview that the home page, files page and uploads page all redirect to a login screen when you are signed out. If any page is visible without logging in, ask for a fix before you go further.

Set up separate views for admin and clients

Ask for two views: one for you, with controls to update status and upload files, and one for clients, which is read-mostly. Keeping them separate prevents clients from seeing admin controls and makes the portal easier for them to use.

Use attached files instead of placeholder text

Placeholder content makes it hard to judge whether the portal works. FromScratch lets you attach files such as PDFs, images and spreadsheets, so the portal shows your real documents. Attach a sample proposal or a sample status report, and check that the file list and download work as you expect.

Refine by chatting. Useful follow-ups include:

  • "Add a status field I can update for each client."
  • "Show only the logged-in client's files."
  • "Put upload dates next to every file."

Make one change at a time. Small, specific requests are easier to check than large rewrites.

Step 3: Test the portal and restore earlier versions

Testing is where most no-code portals fail, so do not skip it.

Log in as a test client

Create a second test account. Log in as that client and check two things: that you see only that client's data, and that you cannot reach admin pages by typing their addresses directly. If the test client can see another client's files, stop and fix that before publishing. This is the most important check in the whole project.

Use version history to undo mistakes

Every change in FromScratch is saved, and you can restore an earlier version. If a refinement breaks the files page, you do not need to rebuild it from scratch. Restore the last working version, then describe the change more narrowly.

Test on a phone as well as a laptop

Clients often check project status on their phones between meetings. Open the preview on a phone, log in, and look at each page. Look for buttons that are hard to tap, text that is cut off and tables that do not fit the screen. Ask for changes in chat if something is wrong.

Publish the portal and use your own domain

When the preview works for both your admin view and a test client, you are ready to publish.

Publish with one click

Publishing gives the portal a public URL that clients can open from any browser. Before you send the link, log in once more from a private browser window to confirm the login screen appears.

Connect a custom domain

Clients trust a portal more when it sits at an address that matches your brand, such as a subdomain on your own website. The steps are in Custom Domain for an AI-Generated Website: Step-by-Step.

Send each client their login and a short guide

Give each client their own login details, not a shared password. Include a short note that covers:

  • Where to log in.
  • What the home page shows.
  • Where to find files and how to upload one.
  • Who to contact if something is wrong.

A short, friendly guide cuts down on "how do I" emails in the first week.

Build it with FromScratch

Here is the full process from start to finish, using FromScratch as the builder.

  1. Open FromScratch from the home page and start a new app. The free plan is enough to build and test your first version.
  2. Paste the prompt below as your first message. It covers users, pages, login and the admin view. Edit the names to match your business.
  3. Wait for the live preview. Review the home page, files page, uploads page and admin view.
  4. Attach real files. Upload a sample proposal, status report or spreadsheet so the files page shows real content.
  5. Refine in small steps. Ask for one change at a time, such as adding upload dates or a status label.
  6. Test as a client. Create a test client account and confirm they see only their own data.
  7. Restore an earlier version if a change breaks something.
  8. Publish to a public URL, then connect your own domain if you want clients to see your brand.
  9. Upgrade only when you need to. Paid plans add credits and projects. Check the pricing page for the current details before you decide.

Use this as your first prompt:

Build a client portal where each client logs in with their own account and sees only their own project status, shared files and messages. Include a home page with current status, a files page where clients can download documents I upload, and a simple contact form. Require login for all client pages, and give me a separate admin view where I can update each client's status and upload files.

If you want to compare builders before you start, Best AI App Builders in 2026: How to Choose covers what to look for.

A client portal is one of several internal and customer-facing tools you can describe in plain language. If your needs are more about tracking leads and contacts, read How to build a CRM with AI: a step-by-step guide. If you want a status overview for your own team, Build a dashboard with AI shows the same approach applied to reporting.

FAQ

Do I need to know how to code to build a client portal?

No. You describe the portal in plain language, review the live preview and refine it through chat. You still need to plan the pages and decide who sees what, but you do not write the code.

Can I build a client portal with AI and keep each client's files private?

Yes, if you ask for it explicitly. Put the per-client rule in your first prompt, then log in as a test client and try to open another client's files. If you can see them, the rule is not working yet, so fix it before you share any link.

Can clients upload files to the portal?

You can ask for an upload form in your first prompt, then test it in the preview with a sample file. Check that the file appears in your admin view afterward. If it does not, describe the problem in chat and ask for a fix.

Can I change the portal after clients start using it?

Yes. Describe the change in chat, such as adding a new status option. If an update causes a problem, restore an earlier version while you fix it. Test the change with a test client before you tell your real clients about it.

Is a client portal the same as a CRM?

Not quite. A CRM tracks your sales pipeline and contacts inside your business. A client portal gives your clients a private view of their own work. Many small teams use both, and the CRM guide explains how the two differ.

Written by

FromScratch TeamEditorial team

The team building FromScratch, the AI app builder that turns a plain-language description into a real, published full-stack app.