Skip to content
All articles

How to Build a Simple Client Portal Without a Portal Tool

8 min readClient work, Hosting

To build a simple client portal, make one folder per client on SnapHost, publish each deliverable into it as a private page, and let the client's whole company in by their email domain. The client gets one address, like yourstudio.snaphost.ai/acme/, followed by the page they want. Each person confirms their email before anything loads, you update a page at the same link instead of resending it, and there is no portal software to set up or keep running.

That is the whole mechanism. The rest of this post is about what a client portal actually has to do, how a folder of pages does it, where this setup stops short of a real portal product, and what it costs.

What a simple client portal needs

Strip the word portal down and most clients want four things. One place to look, so they are not hunting through email for the right attachment. Confidence that the current version is the one they are looking at. Access for the people on their side who need it, without you managing each name. And something that looks like it belongs to you, not to a file-sharing service.

Portal products add a lot on top of that: messaging, invoicing, e-signatures, task lists. If you need those, buy one. If what you deliver is reports, decks, dashboards, prototypes and documents, a folder of private pages covers the four things above, and you can set it up this afternoon.

One folder per client, one address

A Pro workspace on SnapHost has its own subdomain, like yourstudio.snaphost.ai. A page on the workspace's shared drive is addressed by its slug there, and a page filed in a folder is addressed behind the folder's slug. So a folder called Acme with a weekly report in it answers at yourstudio.snaphost.ai/acme/weekly-report, and the Acme folder becomes the client's part of your address.

Make a folder for each client on the shared drive and publish into it. A page on the shared drive is one the workspace shares; a page on your own drive lives under your handle, like /~alex/weekly-report, so keep client work on the shared drive. You can rename a folder's link later, move pages between folders, or move a whole folder, and the addresses you already handed out keep forwarding to wherever the page is now. How to change a page's URL without breaking links goes through what forwards and what does not.

The folder gives the pages a shared prefix. If you want the client to have a front door, publish a short overview page into the folder, with a line and a link for each deliverable, and send them that address. Your AI can write it in a minute, and you update it whenever you add something.

Letting the client's company in

Access is set on each page, from its Sharing card. A restricted page is opened only by the people you name, and each one confirms their email before any content loads. You can name people one at a time, or name a whole company by its domain, like acme.com, and anyone with an address there gets in. Everyone in your own workspace can be given access in one line.

For a portal, the domain entry is the one that matters. Add acme.com to each page in the Acme folder and you stop having to ask who on their side should see it. The new analyst who joins their team next month opens the link and confirms their work email, and nothing on your side changes.

Someone who is not on the list and opens the page can ask for access. The request shows up on your Sharing card, and approving it adds them. That is how a client's outside accountant, on a different domain, gets in without you noticing in advance.

Two more controls sit on the same card when you want them. A view password is a second way in for someone you cannot name. A link expiry puts an end date on a page, which suits a proposal you do not want read six months from now. The details of each are in sharing and access control.

What goes in the folder

A portal is only as useful as what is in it, and the point of using pages is that you do not have to convert anything first. A PDF opens in a viewer on the page. A Word document becomes a readable page. A deck is paged through with the arrow keys. A spreadsheet shows as a grid with its sheet tabs. A notebook, a Markdown file, a diagram, a video, a React component from a chat with your AI, or a full built app: each one becomes a page in the folder.

Keep a page as a draft until it is ready. Nothing is reachable until you publish it, so next week's report can sit in the folder on Thursday and go out on Friday.

Mind what the file itself carries. A Word, PowerPoint or Excel file holds speaker notes, hidden sheets, formulas and comments that the page does not show, and the file stays off the page unless you choose to let readers download it. For a client portal that default is usually right. The report is the deliverable, the workbook behind it is yours.

Keeping it current without resending

This is where a folder of pages beats a folder of attachments. When a number changes, you update the page and the link stays the same. The client's bookmark, the link in last month's email, the address on the overview page: each one now opens the current version. That works on Free as well as on Pro.

On Pro, each update is also saved as a version, and you can roll a page back to an earlier one in one step while it keeps its link. The rollback is saved as a version too. That is the safety net for the day your AI regenerates a report and quietly drops a section.

When an engagement ends, take the pages offline, which switches off their links but keeps the content and settings for the day the client comes back. Or remove acme.com from each page's list, which keeps the pages up and closes them to the client.

Seeing who opened what

A portal product's reporting is one of the things people pay for. Here you get a page's access log: every open is recorded with the time, and with the reader's email when they proved one, and access requests and refusals are recorded too. So "did anyone at Acme read the Q3 report?" has an answer, name by name. An open made with a view password alone is not logged, which is one reason to prefer the domain entry over a password for client work.

The log is per page, which fits the question you actually have: was the proposal read. What an access log for a shared page tells you walks through each event in it.

Putting it on your own address

The subdomain is fine for most studios. If you want the portal on your own domain, there are two ways to do it, both on Pro. A custom domain can point at a single page, like report.yourstudio.com. Or a domain can be bound to the whole workspace, so share.yourstudio.com becomes an alias of your subdomain and every page and folder resolves on it: share.yourstudio.com/acme/weekly-report. That is one DNS record, and a workspace domain can also be given a root page that answers at the bare address.

HTTPS is set up and renewed for you. A workspace gets three custom domains for each paid member, so a workspace of one gets three. Custom domains has the steps.

Where this stops short of a portal product

Be honest with yourself about the gap before you commit. There is no client login area with a dashboard of their projects: a client lands on a page, or on the overview page you made. The overview page is yours to keep up to date each time you add a deliverable. Access is set per page, so a new page in the Acme folder needs acme.com added to it, which is one line each time but a line you have to remember. There is no messaging thread on the page, no e-signature, no invoicing.

If your clients expect to log in somewhere and see tasks, approvals and invoices in one screen, a portal product is the right buy. If they expect to open the thing you made for them, read it on their phone, and trust that it is current, a folder of pages does that with less for both of you to learn.

What it costs

Free gives you up to three pages at a time, three new ones a month, each private to up to three named people or public, on sites.snaphost.ai with a small SnapHost mark. That is enough to try the idea with one client, but a Free workspace cannot use the domain entry or the folder address, and it can invite viewers but not members.

The portal setup described here is a Pro workspace: the subdomain and folder addresses, company-wide access by domain, access requests, passwords, link expiry, version history and custom domains. Pro is 19 euros a month for each person who publishes. Viewers are free, however many there are, and your clients do not need to be members of your workspace at all; they are names and domains on the pages. One person running a studio pays for one seat. Pricing has the current plans.

Your AI can do the publishing on any plan once it is connected. "Publish this into the Acme folder and let acme.com in" is a sentence it can act on.

Setting it up

  1. Create a Pro workspace for your studio if you do not have one. It gets the subdomain, like yourstudio.snaphost.ai.
  2. On the shared drive, make a folder per client. Check the folder's link, since that word is the client's part of the address.
  3. Publish the first deliverable into the folder, as a draft if it is not ready. On a Pro workspace a new page starts out restricted.
  4. On the page's Sharing card, add the client's domain, like acme.com. Add individual addresses for anyone outside it.
  5. Publish a short overview page into the same folder that links to each deliverable, and share that address with the client.
  6. When something changes, update the page. When something new lands, publish it into the folder, add the domain, and add a line to the overview.
  7. After the first week, open the access log on the report and see who read it.

The pieces you are using, folders, the shared drive, roles and the subdomain, are described in personal space, workspaces and folders.

Keep reading