Feature Requests

In security and permissions, the edit status permission needs a checkbox that says "only if created," similar to deleted items. This would help extensively.

More control over who can delete and what can be deleted.

Currently, the Create Views permission for custom roles controls the ability for a user to create a view on a space, but also the ability to create a doc on a task in which that user did not create. It's very strange and awkward that these functions are inextricably linked. They should not be. We want to have a custom role in which users can't clutter up a space with their own custom views, but we also want them to be able to create docs on tasks that they themselves haven't created.

For me the purpose of limited member is having the capability to easily lockdown what a user can access but still have expected functionality on what ClickUp could do if needed. The reason it is beneficial is we could grant access to our clients to export “list based” reports without the team exporting it for them. Administrators can just create duplicate base roles of it if they want some limited members with export and some without.

When editing Settings → Security & Permissions → Custom Role Permissions, the role columns at the top of the table (Guest, Limited Member, Member, Admin, etc.) scroll out of view as you move down the list of permissions. This makes it hard to tell which role you’re adjusting once you’re further down the table, especially in workspaces with multiple custom roles. Requested improvement Make the role header row sticky so the column labels stay visible while vertically scrolling through the permissions list. Why this matters Reduces mis-clicks when toggling permissions for different roles Improves clarity in larger workspaces with many custom roles Quality-of-life improvement for admins who manage roles frequently

Restricting certain type of users (guest, members, custom roles) from moving tasks to other locations to prevent items to inherit custom fields from other locations or missing items in dedicated workflows

I have a list with several views and there is only one that I want to share with a colleague which is filtered with a certain category, but who does not have access to the rest of the views. I need the ability to share one or all of the views in a list to a colleague, giving me the possibility that as a reader, I can't remove the filter from that view that I'm sharing with them.

Current behavior requires users to have edit Custom Fields permission in order to add an existing Custom Field to a List. This creates a conflict. Granting that permission allows users to modify the field configuration globally, which can affect all Spaces, Folders, and Lists that use the same field. Requested enhancement. Introduce a separate permission that allows users to: • Add an existing, globally managed Custom Field to a List Without allowing them to: • Edit the field configuration • Change dropdown options This would enable centralized governance of global Custom Fields while allowing operational teams to apply and use them where needed. This distinction between “use” and “manage” would significantly improve control and scalability for larger Workspaces.

We need to give authorization to see "All Timesheets" to a new customized role and not only to Admin.

We put in some clients to score and approve deliveries we made on ClickUp, but it's a bad thing for the customer to see the team's internal feedback throughout the previous process. It would be great at the permission level to grant that a user can see the task, description, COMMENT, but not view other comments.