The original is one click away. Open original ↗
Five common ClickUp dashboard mistakes and how to fix them
Executive overview
New ClickUp users routinely build dashboards that look right but silently fail — chat widgets no one sees, blank task lists, and endless manual recreation. Each mistake has a simple fix once you know where to look.
The most damaging dashboard mistakes are invisible: permissions gaps and missing watchers mean people simply never see what you built.
The five mistakes
- Forgetting Watchers on chat widgets — if no one is watching the chat widget, no one gets notified of new messages; add watchers via @ mention or the eyeball icon.
- Recreating dashboards manually — use the Duplicate option (three dots next to the dashboard name) to copy an entire dashboard or individual widgets instead of rebuilding from scratch.
- Filtering widget by widget — set a dashboard-wide filter at the top of the dashboard once; it applies to all widgets automatically.
- Ignoring permissions on task list widgets — if a viewer lacks access to the underlying list, the widget shows blank; replace task list widgets with embedded public views so anyone with the dashboard link can see the data without needing list-level permissions.
- Building dashboards without a clear purpose — if a dashboard does not solve a specific, identified problem for a real user, delete it.
Permissions fix: public embed views
- A task list widget pulls live data from ClickUp and requires the viewer to have permissions on the source list.
- A public view generates a shareable link that anyone can see, regardless of ClickUp access.
- Embed that public link inside a private dashboard to combine broad visibility with controlled access.
- This pattern is essential for client portals where clients have no access beyond the dashboard itself.
More like this — when you're ready for early access.
Join the waitlist for a personal account and content recommendations based on what you're working on.
No spam. Unsubscribe at any time.
You're on the list. We'll be in touch before launch.