How to Build a Client Portal in ClickUp Without Buying Extra Seats
- Branden Bell
- Aug 10
- 5 min read
Your client wants to know where their project stands. So they email you. You answer the email, then you update ClickUp, then you answer the same question again next Tuesday.
A client portal ends that loop. ClickUp does it natively, with no add-on and no third-party tool.
What it does not do is let you wing the structure. Get the access model wrong and you either expose internal work you meant to keep internal, or you get billed for seats you never meant to buy.
A ClickUp client portal is a permission decision, not a feature
There is no button in ClickUp labeled Client Portal. You build one out of two native mechanics: guest access and public links.
Everything else follows from which one you pick. So pick first.
Guest access
You invite the client into your Workspace with restricted permissions. They log in, see only what you shared, and can comment or edit if you allow it.
Public links
You toggle a link on and send it. The client opens it in a browser with no ClickUp account, no login, and no invite.
Guest access buys you interaction. Public links buy you zero friction. You rarely need both.
Guests cannot be added to a Space, and that decides your structure
This is the constraint most portal guides skip. Per ClickUp’s own documentation, guests cannot be invited to a Space at all.
Guests can be given access to Folders, Subfolders, Lists, tasks and Docs. Never a Space.
So if your architecture puts one client per Space, you have no way to grant that client access to their own work without moving it. That is a rebuild, not a setting.
Two more limits ride along with it:
Guests cannot access Chat. Members carry location permissions and Chat permissions together. Guests are excluded outright.
Guests cannot edit privacy settings, and they cannot share anything with anyone.
The seat math nobody explains
Paid plans have two kinds of guests, and only one of them is free.
View only guests are free, and paid plans can have an unlimited number of them. Read only, no comments.
Permission controlled guests get one of four levels: view only, comment, edit, or full edit. These consume a seat.
Your included permission controlled guest seats depend on plan and headcount:
Unlimited: 5 seats for a one-member Workspace, plus 2 more for every member you invite.
Business, Business Plus and Enterprise: 10 seats for a one-member Workspace, plus 5 more per member.
Here is the part that costs money. If you run out of permission controlled guest seats and invite one more, ClickUp automatically adds a paid member seat to your Workspace. Unlimited runs $7 per user per month billed yearly and Business runs $12, so the bill moves the moment you cross that line.
There is a quieter version of the same charge. Add a view only guest to a Team and they automatically become permission controlled. Free guest, now billable. If you are still deciding where to sit, I broke down the three limits that actually decide it in this guide to choosing a ClickUp plan.
A comment box is not free. Every client you let comment is a seat, and seats run out quietly.
One more rule catches agencies working with contractors. Anyone using your organization’s email domain or SSO cannot be a guest. If they were already a permission controlled guest, ClickUp converts them to a limited member, and limited members are charged the same as members.
What you can actually share publicly, by plan
Public sharing exists on every ClickUp plan. What you are allowed to share does not.
Docs, wikis, pages, templates and Whiteboards: shareable publicly on every plan, including Free Forever.
Form views: shareable publicly from a Space, Folder, Subfolder or List on every plan.
List, Board, Table, Calendar, Gantt, Timeline, Map and Mind Map views: publicly shareable only from the Everything level, which means Business and above.
A single task: shareable publicly, view only, on every plan.
Spaces: never shareable publicly, on any plan.
That third line is why so many "just share a Board view with your client" tutorials quietly fail for people on Unlimited. On Unlimited, your free portal is a Doc.
Everything shared by public link is view only, and any filters applied to a view travel with the link. Private Lists, Subfolders, Folders and Spaces cannot be shared publicly at all.
Build it in this order
Decide the access model. Comments or approvals from the client means guests. Status visibility only means public links.
Put client-facing work in a List, not a Space. Guests can be added to a List. They can never be added to a Space.
Rename statuses in plain English. Ready for Review beats internal shorthand every time.
Hide the fields they should not see. On any paid plan you can hide individual Custom Fields from all guests and limited members. Margin, internal notes and rate fields belong behind that setting.
Build a Doc as the front door. Docs share publicly on every plan. Put a short welcome note, the process, and the link to their List or view inside it.
Add a Form for intake. Form views share publicly on every plan and from any location, so requests arrive as tasks instead of emails. That is the same trigger I use to start an automated client onboarding workflow.
Set permissions last, and set them low. Comment is the right default for a client. Edit lets them change your data, full edit lets them delete it, and a guest with edit permissions on a Doc can delete Docs and pages.
Five things that quietly break a client portal
Third-party cookies. ClickUp requires them to view publicly shared items. If your client’s browser blocks them, your link looks broken and they will tell you the tool is broken.
The search engine toggle. Public Doc sharing includes a Share link with search engines option. On a client portal, leave it off.
Dashboards are private by default. Spaces, Folders, Lists, tasks and Goals are public by default. Dashboards are the exception, so a client dashboard needs deliberate sharing.
Doc defaults change by plan. On Free Forever and Unlimited a new Doc is public to your whole Workspace. On Business and up it is private by default. Same click, different result.
Link expiration is Enterprise only. Enterprise Workspaces can expire a public link in 7, 30 or 90 days. On every other plan the link lives until you turn it off.
How I structure it on client builds
I do not build a Space per client. One Space holds all client delivery, and each client gets their own List inside it.
That started as a workflow decision. The permissions made it non-negotiable. A List is the smallest container a guest can actually be added to, and it is already where the client’s work lives.
Each List carries a master wrapper task, and the stages of the deliverable sit under it as subtasks. The client sees progress as one story instead of forty loose tasks.
Clients who want a login get comment access to their List. Clients who never will get a Doc with a public link. Most pick the Doc.
I am a PMP and a ClickUp Verified Consultant, and this is the first thing I check when a workspace is handed to me: who outside the company can see what, and what is it costing.
Sources
Want it built right the first time
If your workspace is already live and you want expert eyes on the access model before you invite a single client, that is what ClickUp Consulting is for. If the whole delivery system needs rebuilding, the Client Delivery OS is the 30-day version.
Tell me what you are running and I will tell you what I would change. Get in touch here.
Comments