Feature Requests

See images in attachment. Public folders underneath private spaces inherit sharing permissions from the private space. I've shared the space with Teams ONLY, no individual users. Yet, the sharing modal currently works to actually inherit the individual users that are part of those teams to also be shown as individual people within the sharing modal as well. Feedback from the support team added below: Why individual users appear in the sharing modal This is currently how the sharing modal behaves for public locations. Even though those users are members of a Team that's been added, the modal renders them as individual entries rather than grouping them under their Team. It's a UX limitation, not a sign that someone manually shared with those users individually. When you switch a location (Folder) to private, the modal shows the cleaner Team-grouped view you're expecting. Your assumption about inheritance You're correct. Public locations under a private Space inherit the same access as the Space. So if your Space is private and shared with specific Teams, the public Folders, Lists, and tasks within it are accessible to those same Teams. No additional permission changes are needed for that setup. Getting to clean Team-only sharing For the cleanest view, the key is to set your locations to private and share them explicitly with your Teams. That way, the sharing modal will reflect exactly what you expect: Teams only, no individual user clutter. Just be aware that if anyone has been individually shared at any level (Folder, List, or task), that override will persist even after you restructure, so it's worth spot-checking a few locations after making changes. If you'd like to see improvements to how the sharing modal displays access for public locations, feel free to post your feedback at https://clickup.canny.io/feature-requests so our product team can track it.

When a list is approved for customers, they should be able to see the estimated time (estimate) for a task, but not the actually booked time (tracked time).

Can you please add a permission type that excludes only description edit from Full Edit permission? It is very inconvenient when other people that need access to status changes, custom fields, etc. can change the description whether accidentally or intentionally, as the description is almost always my responsibility. I get notifications about description change and can see details in history but still, it would be better if other people did not have access to the description edit and could only view it. Would be great if only the person that is assigned to the task can edit the description. Another solution would be to lock description from editing, anyone with Full Edit can change this state and it would be used only for intentional editing, maybe another button with lock button next to history and full screen buttons in description?

The ClickUp URL's for a task only contain the (custom) task ID. But that does not make the task human recognizable from the URL. To understand what the task is about you would have to open the link, which takes some time since ClickUp is not very fast when openend in new tab. My suggestion is to include a slug in the URL. The slug should be based on the title of the task. This makes it instantly clear what this task is being linked to. For example: Current task URL - https://app.clickup.com/t/1234/5678abc Suggested task URL - https://app.clickup.com/t/1234/5678abc/my-example-task URL previews often help, but they are not always enabled, depending on the system in which URL's are shared. Note: it should be considered to do the same for links to lists, views, folders, etc.

Notetaker usage per user role or custom role, without having to downgrade users to Limited Member or Guest.Problem: Currently, any Member with access can use AI Notetaker indiscriminately, consuming paid hours without oversight. The only way to restrict it is to change their entire role, which affects all other permissions.Proposed solution: Add an "AI Notetaker" toggle as a custom role permission (similar to how "Manage Users" or "Manage Custom Fields" work), so admins can selectively grant Notetaker access to specific roles or individuals.Impact: Better cost control and adoption governance for organizations paying for AI Notetaker seats/hours.

We recently lost a major event planning task (months of comments, attachments, checklists, and coordination) with zero trace of what happened. No record of who deleted it, when, or whether it was even a deliberate action versus a software bug. The activity feed doesn't log deletions. The Trash has a short retention window and no exportable audit trail. For workspaces running real business operations, this is a serious gap. Request: Implement a permanent, immutable deletion audit log accessible to workspace admins. It should record: what was deleted, who deleted it, when, and from which list/folder. Ideally with a confirmation prompt for tasks that contain attachments or comments. Without this, there's no accountability, no way to investigate data loss, and no way to distinguish accidental deletion from a platform bug or intentional misuse. Every other serious business tool (accounting software, CRMs, ERPs) maintains this kind of trail. ClickUp should too.

It would be highly beneficial to have the ability to add internal members (with emails matching the organization’s domain or using SSO) as limited-access users without consuming a paid license or like an invite people. This feature would allow organizations to better manage costs while still providing controlled access to specific resources for internal collaborators who do not require full member permissions.

When creating a task directly from a chat message using the Create Task feature, there's currently no way to automatically share that task with the person who sent the original message, or with others following the chat. This means the author often has no visibility into a task that was created based on their own message unless someone manually adds them. Requested solution: A setting, configurable at the workspace level, space level, and/or personal level, that controls the default sharing behavior when a task is created from a chat message. Options would include: Auto-share with the message author only Auto-share with the full channel or DM thread Don't auto-share (current behavior) In addition to the default setting, the Create Task dialog itself should include a toggle that lets the user override the default behavior for that specific task, plus a field to manually specify additional people to share the task with. Minimum viable solution: even without the workspace/space/personal default settings, just adding the toggle on the Create Task dialog (share with author, share with channel, or don't share) would solve the core problem. Use case: teams frequently spin tasks out of chat conversations, and the person whose message prompted the task is often left out of the loop unless someone remembers to add them manually. This creates unnecessary follow-up messages just to loop people back in on work that originated from their own request.

The limitation The Progress (Auto) custom field only rolls up completion one level deep: from a top-level parent task down to its direct subtasks. Progress from nested subtasks (level 2 and deeper) is never included in the rollup. Impact Any task in the middle of a multi-tier hierarchy shows a flat 0%, even when its own direct subtasks are marked complete, because from the top parent's perspective those items are nested. This makes Progress (Auto) effectively useless for deep task trees. Confirmed not to be a config issue: the field's Subtasks completion type is enabled, and the "Complete" status is correctly categorized as Done. The 0% is purely due to the one-level rollup limitation. Request Allow Progress (Auto) to roll up nested subtask completion recursively across all hierarchy levels, or at minimum make the rollup depth configurable. Current workarounds Promote mid-tier tasks to top-level so their subtasks become direct children. Use a Progress (Manual) field on mid-tier tasks instead.

We use links to ClickUp document pages and sub-pages in various tasks. However, when a subpage is moved to another document, its URL changes. As a result, all links already stored in tasks no longer work correctly and continue to point to the original document. It would be very helpful if links to pages and sub-pages would persist permanently, regardless of which document the page is in. Alternatively, a redirection from the old URL to the new location could be set up automatically when moving. Use case: We would like to regularly restructure our documents and move subpages thematically to other documents. Links that have already been shared in tasks, other documents, or external sources should still lead to the correct page. Desired behavior: The URL of a subpage remains unchanged when moved to another document, or Existing links are automatically redirected to the new URL. This allows documents to be organized flexibly without having to manually update all linked tasks afterwards.