Feature Requests

Today, ClickUp supports one level of subfolders inside a Folder. Teams with deep organizational structures (agencies managing client → project → workstream, enterprises mirroring department → division → team, construction companies tracking program → site → phase) are forced to either flatten their hierarchy into naming conventions or spin up extra Spaces as a workaround. We'd like the ability to nest subfolders at least 2–5 levels deep so workspaces can mirror real-world org structures without sacrificing a clean, navigable sidebar.

I'd like the option to have "Tabs" in my app just like I would in a browser. I might want to compare and contrast projects or keep omy personal view open while viewing a team project. (But I don't necessary want to save it as a favorite for just a quick review)

--------------------------------- 🔍 Overview --------------------------------- ClickUp's current status system follows a linear progression model with tasks moving sequentially from one status to the next, right? Well, real-world business processes often require dynamic, multi-path workflows with conditional transitions. To bridge this gap, I propose an advanced visual workflow builder—similar to Jira’s workflow editor—that would provide greater flexibility in managing statuses and processes. --------------------------------- 🎯 Key Benefits --------------------------------- 🔹 Non-Linear Transitions – Move beyond the A-to-B status system and allow multiple pathways. 🔹 Visual Workflow Mapping – Enable teams to design and visualize workflows using a drag-and-drop builder (possibly leveraging ClickUp Whiteboards). 🔹 Conditional Status Progression – Set requirements (e.g., field completion or approvals) before tasks can transition to the next stage. 🔹 Native Automation Integration – Leverage ClickUp Automations to streamline process execution. (Technically, it would be possible out of the box but there's room for extension.) 🔹 Improved Process Control – Spaces could define custom process rules, ensuring compliance and structure in task management. --------------------------------- 📌 Suggested Features --------------------------------- 🔹 Visual Builder – A flowchart-style interface for designing workflows intuitively. 🔹 Flexible Status Paths – Allow statuses to branch into different paths based on rules. 🔹 Automated Transitions – Integrate workflow steps with ClickUp Automations for hands-free status updates. 🔹 Conditional Logic – Require specific conditions (fields, approvals, dependencies) before tasks progress. 🔹 Field Locking – Lock down fields after a particular status of the workflow. 🔹 Whiteboard Integration – Embed workflows into ClickUp Whiteboards for real-time collaboration. --------------------------------- 📈 Long-Term Vision --------------------------------- This feature would elevate ClickUp’s workflow capabilities, making it a more powerful tool for more complex business processes. Over time, it could evolve into a fully conditioned process engine, allowing teams to enforce rules and possibly integrate with the upcoming Teams Hub vision, automate tasks, and finally create more bespoke operational flows. --------------------------------- 💡 Why This Matters for ClickUp Users --------------------------------- 🔹 Enhances Workflow Flexibility – Supports non-linear, adaptable processes. 🔹 Boosts Productivity – Reduces manual status management, enhances automation and authenticity to a status being changed. 🔹 Improves Collaboration – Helps teams map out and enforce structured workflows. 🔹 Aligns with Business Needs – Brings ClickUp closer to enterprise-level workflow management tools.

I'd like to turn my Brain AI artifact into a dashboard in the left-hand side shortcuts (Dashboard app); this doesn't seem possible currently

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.

We are using the Calendar view as our main calendar for our team. When we have many tasks on a single day, it becomes VERY difficult to identify which day is which as the number for the day is at the bottom right of the calendar and is very small and hard to see. It would be ideal to have this very prominent in the calendar box (Month view). In addition, it would be nice to see better separation on the different weeks/days as it kind of looks like a big blend sometimes. Also, the "+ x more" is no very prominent either, so it's very easy to miss tasks. Lastly, it would be nice if "Today" was highlighted a bit better, I find it hard to even find the current day easily. It should really stand out more and when you press "today" to jump to today's date, not just this month. It should flash on the current day so it's very clear which day is today (animation), rather than having to now scroll around to find today.

Currently the Gannt, Timeline, and Workload Views default to only working with task and subtask due dates. If you could have the option to replace the due date field with other custom date fields, you'd be able to vastly expand the use cases of these views. Our projects and tasks across all spaces use various custom date fields that allow for more accurate tracking instead of simply "due date". However, if you actually use these custom date fields to build out your clickup infrastructure than most of Clickup's features cease to work properly, as they all function from the core due date field. Please allow us the option to have the gannt chart or timeline place our tasks by any custom date field rather than just the stock "due date field".

Please create an option to automate removing a task from additional list

It would be useful to be able to set the a default Billable/Non-Billable setting on a List basis. So you can default everything in a particular List (and even Space and Folder) to Billable or Non-Billable.

Can you please add an option to turn off the emails that come every time I log in to my account? I routinely switch back and forth between a personal account and an admin account and every time I get an email that says "new login" and it's very annoying!