I’m trying to build a ClickUp client portal to share work-in-progress, completed deliverables, and performance results, without giving clients access to internal processes or clutter.
Dashboards felt a bit too open, so I’m experimenting with public doc views embedded with filtered task views and results.
Has anyone else used this method successfully or found other clean ways to create a client-facing portal in ClickUp?
I’ve done something very similar using ClickUp Docs + embedded filtered views, and it worked great for keeping things clean.
Each client gets a dedicated doc with only the views they need—filtered by tags or custom fields (like “Client Visible”).
I embed list views for tasks in progress, completed work, and even Google Data Studio reports for performance metrics.
It’s been a solid workaround that feels like a portal without exposing our whole workspace.
Bonus: you can password-protect the public doc too if needed.
@sakshikuchroo Yeah, dashboards felt too much for my clients too.
I use a combo of public doc + filtered views, and I also include a “Weekly Summary” section I update manually so clients don’t misinterpret task statuses.
One thing to watch for: make sure no “@internal” comments or subtasks sneak through, set up a custom field like “Client Facing” and filter hard on that.
So far, it’s kept communication streamlined and boundaries clear.
Another route I’ve tested is using Forms + Automations to move tasks into a client-facing folder once they’re marked as ready.
Then I embed a list view from that folder into a doc or even a Notion page if clients prefer.
This keeps the internal mess hidden.
Also, if you use a tool like LambdaTest or a visual QA tool, you can embed test results or screenshots right into the doc to show real progress without needing them to log into multiple platforms.