Feature Requests

Hi, I've started using CU in Safari, but then wanted to use the app, to keep it separate and easier to arrange as wanted. Unfortunately, the app is using a very high amount of CPU. In my M4 Pro, it goes up to about 50%, and remains there. I've cleaned the cache by deleting the whole ClickUp folder in the Library, but with no difference. The Safari page can go up to 50% when in use, and go down to 0% when not in use. I wouldn't dislike to be able to have the app behave the same way. Any chance you can improve the app, so that it behaves like Safari?

Letting the List view search bar find tasks by task name, task description, and Custom Fields is a great idea and super practical. It would be even better if the "Relationships" Custom Field were included in that search too. I used to use a "Dropdown" Custom Field to indicate the company of the task (each option was a company). But since there are so many companies, when the new "Relationships" Custom Field came out I replaced the Dropdown. Now I have a list dedicated to companies, and I use the "Relationships" field to link each task to its company in that list. Unfortunately, I'm thinking about switching back to the "Dropdown" Custom Field, because I found out you can't use the search bar to search tasks by the "Relationships" field, and I always use the search bar to find tasks with the same company.

Hi ClickUp team, I’d like to suggest the following features to help make ClickUp a more complete platform for managing information, using AI, and collaborating with external partners. Workspace-wide file manager / AI Drive A central file management hub where users can visually browse, search, sort, and manage files across the entire Workspace and connected storage services, without having to navigate individual Tasks or Docs. Multimodal AI meeting notes with flexible summary styles It would be helpful if AI Notetaker could use not only meeting transcripts, but also user-written notes, images, screenshots, whiteboards, PDFs, slides, spreadsheets, and other meeting materials to generate summaries. Users should also be able to switch between formats such as Executive Summary, Detailed Notes, Decisions, Action Items, 1-on-1, Sales Meeting, and Custom Templates. Standalone relational databases, separate from Tasks Please consider allowing users to create structured databases without treating every record as a Task. These databases should support relations, rollups, lookups, formulas, filters, and multiple views. Secure AI analysis of password-protected files I’d like to be able to temporarily provide a file’s password so AI can read and analyze its contents while keeping the original file encrypted. The password should not be retained, and no persistent unencrypted copy should be created. Password-protected public sharing Please add stronger controls for publicly shared Docs, Views, Dashboards, Files, and other content. Useful options would include password protection, expiration dates, download restrictions, access logs, and optional authentication through a one-time password or magic link. A dedicated client / external portal A client-facing portal would make it easier to share project progress, timelines, deliverables, documents, files, approval requests, and selected conversations. Clients should only see information explicitly shared with them, with internal information kept separate. Switching between separate ClickUp accounts Please allow users to switch between accounts with different email addresses without repeatedly logging out and back in. This should work across the web, desktop, and mobile apps—not just for switching Workspaces within one account. Custom Fields and structured metadata for Docs I’d like Docs to support metadata such as Status, Owner, Document Type, Department, Project, Review Date, Confidentiality Level, and other Custom Fields. Users should be able to filter, sort, and group Docs by these fields. Two-way synchronization with Notion databases Please support true two-way synchronization between Notion databases and ClickUp, including configurable field mappings, updates in both directions, and relationships linking Notion pages to ClickUp projects or Tasks. Two-way channel synchronization between Slack and ClickUp Chat It would be useful to connect a Slack channel to a ClickUp Chat channel and keep conversations synchronized in both directions, including messages, threads, attachments, and links wherever technically possible. Guest access to Super Agents Please allow Guests to interact with Super Agents while strictly respecting their existing permissions. Agents should only use Tasks, Docs, Files, and other information that the Guest already has permission to access. These capabilities would help us keep more of our work in ClickUp while improving information organization, secure sharing, and collaboration across teams and external partners. Thank you for considering these suggestions.

Currently, the table layout for subpages lists subpage title, owner and contributors. It would be beneficial to be able to add columns to the table view that would then be auto-populated with a metafield in the subpage (like a page description).

We used this all the time in the past and now it seems to be gone. I have no interest in channel chats or whatever it's called. I want to be able to make a comment within a list so everyone can easily see it when they go to that specific list. No one wants to favorite a channel to every list they have open. That is a terrible UI change! Please bring back List Level Comments!

I need a feature that would allow me to back up my entire workspace locally. tks

We are building an ecosystem of ClickUp Super Agents, starting with Absencia and Onboardia, and need natural participation in ongoing Chat threads without repeated mentions. Submitted following Niko's recommendation in ClickUp Support ticket #2769821. Expected behaviour • Once an agent is @mentioned, clearly addressed by its plain-text name, or joins a conversation, it follows that thread within its permitted scope. • It receives and reads later replies, including contextual follow-ups such as “What do you think?” with no name or @mention. It then answers the latest relevant question, or acknowledges it with an appropriate native emoji or brief reply. • This also works between agents. When one agent directly addresses another, the recipient acknowledges that message. Acknowledgments are terminal; they must not create an endless agent-to-agent loop. • Replies remain in the original thread, authored by the actual native Super Agent, with genuine recipient mentions where appropriate. Following a thread must not expand permissions or grant operational authority. Requested native capability Please provide durable Super Agent thread subscriptions and a reliable “reply posted in a followed thread” event, independent of repeat mentions. Ideally this should include automatic enrollment, permitted-channel controls, follow/unfollow or mute controls, restart/catch-up behaviour, deduplication, native reply/reaction support, and bounded agent-to-agent acknowledgment. Reading every new message in a followed thread should be separate from deciding whether to interrupt or reply. How this differs from Ambient Replies ClickUp Support explained on 5 October 2026 that Ambient Replies covers follow-ups from the same person after a real @mention. The remaining gaps are replies from other thread participants, automation-started conversations, plain-name enrollment, lasting subscriptions and subscription controls, and bounded agent-to-agent acknowledgments. Support also explained that a guard may leave follow-ups unanswered and selects one agent per message. We need each relevant subscribed agent to receive the event, with a separate relevance decision and loop limits controlling its response. This request extends native conversation delivery beyond the current Ambient Replies scope. Working external workaround We currently use a small Python background worker on Render with one instance and persistent SQLite state. Within explicitly permitted channels, the ClickUp Chat API discovers roots and reads thread replies and native tagged users. Mentions, clear names and native participation establish durable per-agent subscriptions. New messages enter a deduplicated persistent outbox keyed by workspace, channel, thread, source message and agent. Polling is bounded and rate-limited, with a grace period for native handling. Where delivery is needed, the worker sends a technical envelope with source identifiers to the native agent's verified private invocation DM. The agent fetches the real thread context and replies or reacts in the original thread. Reasoning stays with the native ClickUp Super Agent; there is no external LLM. Employee narratives are not copied into the envelope or stored in the relay database/logs. Delivery intent is recorded before sending, uncertain outcomes are reconciled before retries, and native replies/reactions are independently verified. Human questions take priority, and self-messages and terminal acknowledgment loops are suppressed. We have verified unnamed follow-up replies by both native agents in our configured shared channel, restart deduplication, and bounded mutual acknowledgment. Coverage is scoped, not workspace-wide. We are retaining this relay for now and deferring migration to native handling. Why native support matters This should not require customers to operate extra hosting, credentials, polling, persistent state and deployments. A native implementation should preserve permissions, privacy and original-thread context while making event delivery observable and reliable. Acceptance should cover same-user and different-user follow-ups without re-mentioning, automation-origin threads, more than one relevant agent, restart/catch-up without duplicates, and terminal agent-to-agent acknowledgments. We would be happy to test native support so we can eventually retire the external relay.

Hi ClickUp team, every notification email about the same task (new comment, status change, assignment and so on) currently arrives as a separate message. On busy tasks this floods the inbox, and it is hard to follow what happened on a task. Jira, GitHub and others group all emails about one issue into a single conversation. This would be a great improvement for ClickUp too, and it is simple to implement with standard email headers: Same subject for every email about a task, for example [Task-ID] Task name. Put the kind of change into the body or the preview text instead of the subject, because Gmail and others only group mails with the same subject. The first email about a task gets a stable Message-ID, for example < task-123@clickup.com >. All later emails send In-Reply-To and References pointing to that ID. Outlook additionally uses Thread-Topic. With this, Gmail, Outlook and Apple Mail show all updates for a task as one thread, and a task's history can be read at a glance in the inbox. Thanks for considering it! Best regards, Alexandra Belousowa

Right now due date automations amount to “trigger date plus X days”. Far better for many purposes if the rule could be, e.g.: “Set Due Date to Next Monday” “Set Due Date to Third Wednesday of next month” etc. Because often a process is more interested in a day of the week, than exactly when the last step was completed.

With the ability to create a ton of docs and pages via AI. Having to also update the pages style for example a page outline (turn it on) for every page becomes manual work thats pretty brutal to do. I propose that you allow to set a doc to a style for all its pages. so it becomes a turn page outline once rather than multiple times. Or let the Brain AI work on page style settings