In short
A useful client portal can be one page with three parts: the current status, the client's next action, and links to the documents they may need.
Use a public static page only for information that is safe for anyone with the link to read. Choose a system with accounts and permissions when clients must upload files, pay, or view private records.
We built a fictional packaging-project page for a small design studio. The page tells the client that concept review is ready, asks them to choose a direction, and keeps three document links below the action. We then changed the status in the existing page and reopened the original reader address.
What should a simple client portal include?
Start with the reason the client opened the page. A compact portal does not need to reproduce the team's project board. It needs to answer three questions in this order:
- Where does the work stand? Name the current stage and say what has or has not happened.
- What should the client do next? Give one specific action and the date you need it.
- Where are the useful documents? Link the current brief, review material, invoice, or delivery file with clear labels.
This keeps the original purpose of a client portal: one address that holds the current state and the material a client would otherwise search for in email.
How do you share a client portal without a login?
Open Share and create the reader link. In the panel used for this example, anyone who has the link can read the page without signing in, and readers cannot edit it. Search indexing was off.
That is convenient, but it is not private storage. A hard-to-guess address is not a permission system. Do not place personal data, confidential contracts, account details, or sensitive client files on a public reader page. If the page links to an external document, set that document's access separately and test it as the client.
How do you keep the same client portal address current?
Edit the existing page instead of making a new one. We opened Edit on the fictional portal, selected the current-status area, added “Cover direction B is approved,” and chose Done.
The original reader address then showed the added status line. This is the practical reason to send a page rather than a new attachment for every correction: the client can return to the address already in the conversation.
What belongs on the page, and what stays elsewhere?
Keep the portal readable. Put the summary and action on the page. Use labeled links for material that already has the right access controls. Keep internal task notes, draft comments, passwords, customer records, and private uploads out of the static page.
Email still has a job: tell the client what changed and point them back to the page. The page is the current reference; the message is the notification. This avoids making the inbox the only place where the latest status can be found.
You can download the complete fictional client portal example and replace its names, dates, status, action, and document destinations. Review every link before sharing it.
When not to do this
Do not use a public static page as a substitute for a secure client system. Choose a portal with authentication, permissions, and suitable storage when clients need to upload files, sign documents, make payments, exchange regulated information, or see records that must be restricted to a named person. A static page also stops being a good fit when many people need different access or when updates must come from a database.
Where NOS fits
NOS can turn one self-contained HTML page into a reader address. For this example, the Share panel created a read-only link, Edit changed the existing page, and the same reader address showed the saved update. That makes it suitable for a public, low-risk status page; it does not add a login, client uploads, payment processing, or private document permissions.
What should you build next?
If this page is part of a new relationship, start with the client onboarding template so the process, timeline, and requests are clear from day one. For one purchase rather than an ongoing project, an orders link narrows the page to what was ordered and its current stage. If the main problem is sending a document, use the file-sharing guide and choose the document's access before sending the address.